Commits on Source (6)
-
Tim Jaacks authored
We don't need to explicitly trigger a build after merging changes in gitlab-ci. A master pipeline on the target projects runs automatically.
45b49ee3 -
Tim Jaacks authored
- Use "source" and "target" terminology in the script, just like in the GitLab CI variables. - Spefify data types for function arguments. - Rename function arguments to better reflect their data types. - Move determination of integration branch into main function, so that the successfull status message can be more verbose. - Remove parent_merge_request feature and checking for gitlab-ci integrations, because the check job does not run on gitlab-ci integration branches at all.
593784e1 -
Tim Jaacks authoreda6721243
-
Tim Jaacks authored76bd81d8
-
Tim Jaacks authored21e7edeb
-
Tim Jaacks authoredf8d6de86
Showing
- .gitlab-ci.yml 0 additions, 48 deletions.gitlab-ci.yml
- build-jobs-ci-test.yml.jinja2 6 additions, 4 deletionsbuild-jobs-ci-test.yml.jinja2
- manifest-integration-jobs.yml.jinja2 0 additions, 36 deletionsmanifest-integration-jobs.yml.jinja2
- manifest-integration.yml 29 additions, 0 deletionsmanifest-integration.yml
- scripts/check_if_integration_branch_is_up_to_date.py 59 additions, 67 deletionsscripts/check_if_integration_branch_is_up_to_date.py
- scripts/retrigger_integrating_projects.py 0 additions, 1 deletionscripts/retrigger_integrating_projects.py