ci: deploy snapshots using GitHub actions in conjunction with Buildkite #3067
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.
What does this PR do?
Use GitHub actions and Buildkite to run the snapshot releases.
GitHub actions will be the only interface that the team will need to interact with, and there is a new GitHub action in charge of triggering the snapshot release in Buildkite.
This particular approach has been validated and done in some other projects, see elastic/ecs-logging-java#197
Caveats
Only supported for snapshot releases. Hence, the release automation will be done in a follow up.
Duplicated
.ci/settings.xml
to avoid messing around with the release automation.