Skip to content
This repository has been archived by the owner on Sep 17, 2024. It is now read-only.

Support running the E2E against the local artifacts generated by the Beats repository #653

Closed
mdelapenya opened this issue Jan 25, 2021 · 1 comment · Fixed by #688
Closed
Assignees
Labels
automation enhancement New feature or request

Comments

@mdelapenya
Copy link
Contributor

mdelapenya commented Jan 25, 2021

It would be a nice-to-have to run the E2E against the Beats locally generated artifacts, improving the developer experience.

To generate the artifacts:

export THE_BEAT="elastic-agent"
cd x-pack/$THE_BEAT; SNAPSHOT=true PLATFORMS=darwin   DEV=true mage package

for docker images set platform:

PLATFORMS="+all linux/amd64"

An initial idea could be passing an environment variable with the location of the local Beats repo, so that it's possible to get the artifacts from that path. Something like BEATS_LOCAL_PATH=/tmp/foo

@elastic/observablt-robots @michalpristas @EricDavisX @ph, thoughts?

@mdelapenya mdelapenya added enhancement New feature or request automation labels Jan 25, 2021
@mdelapenya mdelapenya self-assigned this Jan 25, 2021
@mdelapenya
Copy link
Contributor Author

In the conversation we mentioned the idea of adding a command in Beats' build system, so that it fetches current version of the E2E tests (per maintenance branch) and automatically triggers them.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
automation enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant