-
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
CI: disable e2e for elastic-agent on tags/branches #28481
CI: disable e2e for elastic-agent on tags/branches #28481
Conversation
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
💚 Flaky test reportTests succeeded. 🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
(cherry picked from commit d1bcb50)
(cherry picked from commit d1bcb50) # Conflicts: # Jenkinsfile # x-pack/elastic-agent/Jenkinsfile.yml
(cherry picked from commit d1bcb50) # Conflicts: # Jenkinsfile # x-pack/elastic-agent/Jenkinsfile.yml
@Mergifyio backport 7.x |
@Mergifyio backport 7.15 |
✅ Backports have been created
|
✅ Backports have been created
|
What does this PR do?
Disable e2e for elastic-agent in the main pipeline (ONLY) for the merge commits into branches or tags. In other words, the e2e testing for elastic-agent will be enabled only on a PR basis.
Though, the e2e testing for elastic-agent happens in the e2e specific pipeline, that happens when there is a merge commit.
Why is it important?
After merging #24112 it seems the e2e for the elastic-agent are failing and might mislead the status in the GitHub checks for the merge commits in the branches.
See