-
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
fix(ci): include complete as supported variant on merges #27572
Conversation
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪💚 Flaky test reportTests succeeded. Expand to view the summary
Test stats 🧪
|
I have opened issues for the flaky tests and suggest we skip the tests, PR created #27590. |
* master: Skip Flaky Tests (elastic#27590) Remove fargate from aws module config (elastic#27575) [Heartbeat] Fix scheduler job type limit algorithm (elastic#27559)
* fix(ci): include complete as supported variant on merges * chore: simplify (cherry picked from commit 5937778)
* fix(ci): include complete as supported variant on merges * chore: simplify (cherry picked from commit 5937778)
* fix(ci): include complete as supported variant on merges * chore: simplify
What does this PR do?
it includes
complete
variant as a supported variant when merge commits are packaged.Why is it important?
The elastic-agent-complete image seems to override the regular image. See my comments on #27427 (comment)
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Author's Checklist
Related issues