-
Notifications
You must be signed in to change notification settings - Fork 76
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
ci: release automation #197
Conversation
similar to the apm-agent-android one
@@ -0,0 +1,13 @@ | |||
agents: | |||
provider: "gcp" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: does this need to run on gcp
?
from my experience with playing around with buildkite, this provider takes a bit longer to get scheduled than other workers.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is needed, since the existing default containers don't have the whole OS setup, such as gpg
.
Potentially, we could create a container image to support that particular use case, but as it works with GCP
workers, I'd consider that particular implementation to be done in a follow up. So we can keep migrating other projects.
What
Use Buildkite to run the releases interacting with Maven central.
Why
Jenkins is deprecated hence we use Buildkite for releases, while we use GitHub actions for the CI.
Buildkite will act as a provisioner, pretty much:
release.sh
orsnapshot.sh
scriptsAs a consequence, this project will contain all the moving pieces for the release, including the scripts needed for the releases/snapshots.
Use cases
Tasks