Backport PR #15827 to 7.17: Fix IT tests after version bumps #15838 #15839
Conversation
This file contains 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 commit fixes IT failures that frequently occur after version bumps due to missing unified release snapshot builds for the new version. This commit uses project specific DRA snapshot URLs for ES and Filebeat in all cases apart from release builds. (cherry picked from commit d74fea4) Co-authored-by: Dimitrios Liappis <dimitrios.liappis@gmail.com>
💛 Build succeeded, but was flaky
Failed CI Stepscc @dliappis |
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.
Backport PR #15827 to 7.17 branch, original message:
Release notes
[rn:skip]
What does this PR do?
This commit fixes IT failures that frequently occur after version bumps due to missing unified release snapshot builds for the new version.
This commit uses project specific DRA snapshot URLs for ES and Filebeat
in all cases apart from release builds.
Why is it important/What is the impact to the user?
This is a very important to fix as several pipelines (PR, exhaustive, JDK matrix, aarch64) run IT tests as a prerequisite and produce unnecessary failures shortly
after version bumps, possibly blinding us from genuine issues.
How to test this PR locally
See CI from backporting this PR to
8.12:and compare to https://buildkite.com/elastic/logstash-exhaustive-tests-pipeline/builds/126#018d31b4-8da9-4dbf-b43e-217f2a4f7518/46-469 showing current failures on the
8.12branchRelated issues