You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 17, 2024. It is now read-only.
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
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.
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:
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?
The text was updated successfully, but these errors were encountered: