chore: pass BEAT_VERSION when running E2E tests (backport #26291) #26889
Conversation
![mergify[bot]](https://avatars.githubusercontent.com/in/10562?s=60&v=4){kind=small}
(cherry picked from commit ea84a3b)
botelastic
bot
added
the
needs_team
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪💚 Flaky test reportTests succeeded. Expand to view the summary
Test stats 🧪
|
|
Hi! We're labeling this issue as |
| @@ -524,6 +524,7 @@ def e2e(Map args = [:]) { | |||
| def goVersionForE2E = readFile('.go-version').trim() | |||
| withEnv(["GO_VERSION=${goVersionForE2E}", | |||
| "BEATS_LOCAL_PATH=${env.WORKSPACE}/${env.BASE_DIR}", | |||
| "BEAT_VERSION=${env.VERSION}-SNAPSHOT", | |||
There was a problem hiding this comment.
Umm, triggerE2ETests also appends -SNAPSHOT, do we have the risk of appending it twice?
There was a problem hiding this comment.
No, there is no risk, as we set that version to be used as input parameter of the downstream job for the e2e tests
Well, this should be applied in 7.14 for consistency as it was applied to 7.13, 7.15 and 7.x. |
|
Hi! We're labeling this issue as |
|
@mdelapenya can this be closed? |
botelastic
bot
removed
the
needs_team
Co-authored-by: Jaime Soriano Pastor <[email protected]>
|
@jsoriano if you agree, I'm merging this one |
…) (elastic#26889) * chore: pass BEAT_VERSION when running E2E tests (elastic#26291) (cherry picked from commit b35a1bf) * fix: proper param type Co-authored-by: Jaime Soriano Pastor <[email protected]> Co-authored-by: Manuel de la Peña <[email protected]> Co-authored-by: Jaime Soriano Pastor <[email protected]>
This is an automatic backport of pull request #26291 done by Mergify.
Mergify commands and options
More conditions and actions can be found in the documentation.
You can also trigger Mergify actions by commenting on this pull request:
@Mergifyio refreshwill re-evaluate the rules@Mergifyio rebasewill rebase this PR on its base branch@Mergifyio updatewill merge the base branch into this PR@Mergifyio backport <destination>will backport this PR on<destination>branchAdditionally, on Mergify dashboard you can:
Finally, you can contact us on https://mergify.io/