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

Move to a GCP agent the release step #1194

Merged
merged 7 commits into from
Mar 21, 2023

Conversation

mrodm
Copy link
Contributor

@mrodm mrodm commented Mar 21, 2023

This PR moves the goreleaser step to be run in a GCP agent.

Increasing memory was not successful: https://buildkite.com/elastic/elastic-package/builds/473#018704b5-4263-4d7e-9f30-b171bd8eb5b3

Successful build https://buildkite.com/elastic/elastic-package/builds/478
Triggering directly this command: goreleaser releaser --skip-publish --snapshot

@mrodm mrodm requested a review from a team March 21, 2023 16:13
@mrodm mrodm self-assigned this Mar 21, 2023
Comment on lines +5 to +17
cleanup() {
rm -rf ${WORKSPACE}
}
trap cleanup exit

WORKSPACE="/tmp/bin-buildkite/"

VERSION=""
source .buildkite/scripts/install_deps.sh
source .buildkite/scripts/tooling.sh

add_bin_path
with_go
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Moving to GCP agents requires to install go as a first step.

@mrodm mrodm marked this pull request as ready for review March 21, 2023 16:15
@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

History

cc @mrodm

@mrodm mrodm changed the title Move to gcp release step Move to a GCP agent the release step Mar 21, 2023
@mrodm mrodm merged commit 0f462b8 into elastic:main Mar 21, 2023
@mrodm mrodm deleted the move_to_gcp_release_step branch March 21, 2023 16:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants