[RORDEV-1229] Run e2e tests against branch-matched plugin builds - #96
Merged
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
A healthy full suite is 16-33 min, but an attempt that wedges (stack comes up fine, then Kibana stays alive and healthy while it stops serving) ran the full 60-minute budget before retrying, pushing jobs to 85-95 min and leaving the retry too little room. 35 min cuts the wedged attempt loose early and gives the retry a full budget of its own. targeted-e2e-tests.yml keeps 60 — it runs max_attempts: 1, so there is no retry to hand the saved time to and a premature kill is unrecoverable. The monitor now records RestartCount, StartedAt and Health/FailingStreak per container, and dumps Warning events on the eck side. Status alone could not distinguish a container that bounced between two 10s samples from one that never moved, which is exactly what blocked the last diagnosis. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Dzuming
requested changes
Jul 30, 2026
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
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.
Until now the tests always ran against whatever plugin images happened to be published. There was no way to check a plugin change before it was released, and the develop suite used a shared tag that could be replaced by another run while the tests were still going.
This changes how the pipeline picks the plugins to test:
The waiting and triggering logic lives in one shared script, so the plugin repositories can reuse it instead of keeping their own copies.
The rest of the changes make the suite finish more often and fail more clearly:
E2E tests and changes to existing tests were ported from the ROR KBN repo.
One test was removed because the feature it covered no longer exists.