CI and release process #12
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kmoe
force-pushed
the
ci-release
branch
2 times, most recently
from
20a25b1 to
ce2f18b
Compare
paultyng
reviewed
Jul 10, 2020
kmoe
force-pushed
the
ci-release
branch
14 times, most recently
from
b04f8f6 to
c0c5d15
Compare
radeksimko
approved these changes
Jul 13, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
fixes #11
Based on the SDK CircleCI setup.
PR builds
On each PR, a matrix of builds is run:
There is a macOS executor on CircleCI, but it doesn't have Go installed, and the architecture is sufficiently similar to Linux to leave this out for now. If we want to test all PRs on macOS we can add this later.
Release builds
As in the SDK, to release from
masterone needs only to update CHANGELOG.md to include a#x.y.z (Unreleased)line and then trigger thetrigger_releasebuild.The release workflow will then:
tfinstall/version.go(this will be removed in use runtime.BuildInfo for version #22)Git commits and tags are signed using the bot's GPG key.
The release workflow was tested by temporarily adding
ci-releaseto its allowed branches, preparing the branch for a v0.0.1 release, and verifying the changes committed and pushed to this branch by the bot.