-
Notifications
You must be signed in to change notification settings - Fork 27
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
10 additions
and
10 deletions.
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,19 +1,19 @@ | ||
# Releasing | ||
|
||
1. Generate release notes using [ghch](https://github.com/buildkite/ghch) `~/go/bin/ghch --from=v1.1.1 --next-version=v1.1.2 --format=markdown` | ||
1. Generate release notes using [ghch](https://github.com/buildkite/ghch) `ghch --from=v1.1.1 --next-version=v1.1.2 --format=markdown` | ||
1. Examine the release notes to determine what the version should be, re-run | ||
`ghch` if necessary. | ||
1. Create a release branch `git checkout -b keithduncan/release/1.1.2` | ||
1. Create a release branch `git checkout -b release/$VERSION` | ||
1. Update [version/version.go](version/version.go) with the new version number | ||
1. Update [CHANGELOG.md](CHANGELOG.md) with the release notes | ||
1. Push your branch and open a pull request | ||
1. Once CI has passed, merge your pull request | ||
1. Open the default build for the merge commit on the [main pipeline](.buildkite/pipeline.yml) | ||
1. Wait for the tests to pass, then unblock the pipeline to release | ||
1. Wait for the build to finish and create a git tag for us | ||
1. Update the created GitHub release, and copy the changelog entry into the description | ||
1. Create a new build on the [buildkite-agent-scaler-publish pipeline](https://buildkite.com/buildkite-aws-stack/buildkite-agent-scaler-publish) supply `refs/tags/$TAG` for the *Branch* field | ||
1. Create a git tag `git tag -sm $TAG $TAG`, where `$TAG=v$VERSION`. Make sure the tag has a `v` and the version does not. | ||
1. Push your tag to GitHub: `git push --tags` | ||
1. Check the following builds: | ||
1. The SAR publishing pipeline: [buildkite-agent-scaler-publish pipeline](https://buildkite.com/buildkite-aws-stack/buildkite-agent-scaler-publish) | ||
to update the AWS Serverless Application Repository | ||
1. Ideally this pipeline would be automatically triggered but the pipelines | ||
are in separate Buildkite organisations in order to use different agent pools | ||
1. Unblock the pipeline to release to the AWS Serverless Application Repository | ||
1. The tag build on the [usual pipeline](https://buildkite.com/buildkite/buildkite-agent-scaler) | ||
1. Check the [release page on GitHub](https://github.com/buildkite/buildkite-agent-scaler/releases) for a draft release that's been created | ||
1. If you approve of the draft github release, unblock the steps in both builds. | ||
1. Once both builds are green, publish the draft GitHub release |