CI: Check: integration branch may have multiple commits
As all projects are commited in the same branch the 'up-to-date' check may not only check if the first parent commit points to the master/dunfell branch. Now it is needed to loop through the history until the integration branch's commit is found. On fail a message is displayed which merge request needs to be retriggered manually. This can now also be the 'parent'-MR that triggered the complete chain. The check job is used pipeline again. The retrigger job also looks in the .gitlab-ci project for check jobs to retrigger.
Showing
- .gitlab-ci.yml 32 additions, 3 deletions.gitlab-ci.yml
- check_if_integration_branch_is_up_to_date.py 44 additions, 12 deletionscheck_if_integration_branch_is_up_to_date.py
- deploy_gitlab_ci.py 4 additions, 4 deletionsdeploy_gitlab_ci.py
- foobar-manifest-integration.yml 14 additions, 5 deletionsfoobar-manifest-integration.yml
- foobar-manifest.yml 4 additions, 0 deletionsfoobar-manifest.yml
- gitlab-ci-integration.jinja2 4 additions, 0 deletionsgitlab-ci-integration.jinja2
- update_submodule.py 3 additions, 3 deletionsupdate_submodule.py
Loading
Please register or sign in to comment