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

Auto-release CLI on new version of golang #642

Merged
merged 1 commit into from
Mar 15, 2024

Conversation

ystros
Copy link
Contributor

@ystros ystros commented Mar 14, 2024

Adds task to the automatically-release-new-patch job that compares the golang version of the previously released BOSH CLI binary with the golang version of what would be released. If they're different (in the case of a bumped golang version, or intentional roll back), then an automatic release would be triggered, similar to when CVE fixes are detected.

Additional Context

I noticed that we haven't released a version of the bosh CLI compiled using golang 1.22.1. Many BOSH-related repos have automatic releasing of patches when a golang bump occurs, the intention is to make the CLI consistent with those.

This utilizes a new shared task I just added to the golang-release: cloudfoundry/bosh-package-golang-release@7360ed8

A test run of the task (minus the success clause that causes a release) can be seen here: https://bosh.ci.cloudfoundry.org/teams/main/pipelines/bosh-cli/jobs/automatically-release-new-patch/builds/14

Adds task to the `automatically-release-new-patch` job that compares the
golang version of the previously released BOSH CLI binary with the
golang version of what would be released. If they're different (in the
case of a bumped golang version, or intentional roll back), then an
automatic release would be triggered, similar to when CVE fixes are
detected.
@rkoster rkoster merged commit 29cb5cf into main Mar 15, 2024
5 checks passed
@ystros ystros deleted the auto-release-when-golang-is-bumped branch March 15, 2024 14:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging this pull request may close these issues.

3 participants