Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Buildkite needs a 'mage package' step separate from integration tests #4142

Closed
2 tasks done
cmacknz opened this issue Jan 25, 2024 · 1 comment · Fixed by #5129
Closed
2 tasks done

Buildkite needs a 'mage package' step separate from integration tests #4142

cmacknz opened this issue Jan 25, 2024 · 1 comment · Fixed by #5129
Assignees
Labels

Comments

@cmacknz
Copy link
Member

cmacknz commented Jan 25, 2024

Right now Buildkite does not run mage package for all platforms, the package target is only executed for the platforms covered by integration tests.

  • Add a mage package build step that mimics what the unified snapshot release job does to ensure new changes do not break the build.
  • The .tar.gz and .zip artifacts for each PR should be available as Buildkite artifacts. This would simplify manual testing of PRs by allowing the changes to be downloaded and installed easily.
@elasticmachine
Copy link
Contributor

Pinging @elastic/elastic-agent (Team:Elastic-Agent)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants