Separate out test case generation from deployment
Rather than looping over branches (in included template from `pages`),
generate the test cases here, provide these as an artifact and deploy
in a separate job. This avoids the regeneration of pages that have
not changed.
Use the apertis-test-cases-web as part of a multi-project pipeline to
deploy. Remove the deployment tools from this branch.
Whilst we are here, utilise an environment variable for the release to
make it easier to migrate this between releases.
Signed-off-by:
Martyn Welch <martyn.welch@collabora.com>
Showing
- .gitlab-ci.yml 17 additions, 6 deletions.gitlab-ci.yml
- atc 0 additions, 1 deletionatc
- atc_extra/__init__.py 0 additions, 38 deletionsatc_extra/__init__.py
- atc_extra/css/bootstrap.min.css 0 additions, 7 deletionsatc_extra/css/bootstrap.min.css
- atc_extra/css/bootstrap.min.css.map 0 additions, 1 deletionatc_extra/css/bootstrap.min.css.map
- atc_extra/templates/menu.html 0 additions, 25 deletionsatc_extra/templates/menu.html
- atc_menu 0 additions, 58 deletionsatc_menu
- static/404.html 0 additions, 34 deletionsstatic/404.html
Loading
Please register or sign in to comment