Trigger Campaigner CI pipelines from a main schedule job #581
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
antonipp
force-pushed
the
ai/refactor-campaigner-ci
branch
from
0e9f1b0 to
2159f93
Compare
jaredledvina
approved these changes
Oct 29, 2024
|
Replaced with #582 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The new
trigger-buildsCI job will be scheduled on each one of our main branches (ex:v1.15-dd). It will find the 3 latest tags and will make an API call to Gitlab to trigger child pipelines for each tag. These pipelines will build the images and will execute the associated Campaigner runs.