[CI] Add branch filtering logic to DRA trigger pipeline #127308
Merged
Conversation
This file contains hidden or 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
This filtering will be used to trigger DRA for 7.17 weekly instead of twice a day.
|
Pinging @elastic/es-delivery (Team:Delivery) |
breskeby
approved these changes
May 5, 2025
| source .buildkite/scripts/branches.sh | ||
|
|
||
| # We use that filtering to keep different schedule for different branches |
There was a problem hiding this comment.
I wonder if we need this. isn't that only used for triggering a DRA build from an intake? If we have something to commit to 7.17, we might want to keep building DRA artifacts immediately?
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.
This filtering will be used to trigger DRA for 7.17 weekly instead of twice a day.