-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(ci): use same branching schema for e2e #28493
chore(ci): use same branching schema for e2e #28493
Conversation
Do not merge until e2e-testing project renames its branches |
💚 Build Succeeded
Expand to view the summary
Build stats
❕ Flaky test reportNo test was executed to be analysed. 🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
(cherry picked from commit 055e859)
(cherry picked from commit 055e859)
* upstream/7.x: chore: use same branching schema for e2e (#28493) [Automation] Update elastic stack version to 7.16.0-8bf0b9b1 for testing (#28484) chore(ci): remove not used param when triggering e2e tests (#27823) (#27828) Add deprecation warning for filebeat disabled modules (#28393) Run Python tests in libbeat (#28438) (#28485) Register `storage_account` as second name for `storage` metricset (#28447) (#28470) [CI] Add E2E for x-pack/elastic-agent (fleet) (#24112) (#28465)
(cherry picked from commit 055e859) Co-authored-by: Manuel de la Peña <[email protected]>
(cherry picked from commit 055e859) Co-authored-by: Manuel de la Peña <[email protected]>
(cherry picked from commit e51835b) Co-authored-by: Manuel de la Peña <[email protected]>
What does this PR do?
When triggering the e2e tests for Beats branches, we want to follow the same branch name schema than in Beats.
For that reason we are renaming e2e's maintenance branches from 7.15.x to 7.15
Why is it important?
Consistency across related projects, aligining with stack versions