haskal
/
vagrant
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Update the steps in the release document

This commit is contained in:
Chris Roberts 2019-06-25 14:26:37 -07:00
parent 55019bc846
commit 8e59d9e159
1 changed files with 11 additions and 25 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

36
RELEASE.md
View File

@ -15,34 +15,20 @@ targeted at Vagrant core members who have the ability to cut a release.
$ git push --tags $ git push --tags
``` ```
1. Trigger an installer creation run within the HashiCorp Bamboo installation. 1. This will automatically trigger an installer creation, upload the artifacts,
This will take around 45 minutes. and publish the release.
1. Download all the resulting artifacts into the `pkg/dist` folder relative to 1. After the release has been published update the `website/config.rb` to point
the Vagrant repository on your local machine. to the latest version, commit, and push.
1. Run `./scripts/sign.sh` with the version that is being created. This must be 1. Publish the webiste by deleting the `stable-website` branch, recreate the branch,
run from the Vagrant repo root. This will GPG sign and checksum the files. and force push. From the `master` branch, run:
1. Run the following command to upload the binaries to the releases site: ```
$ git branch -D stable-website
``` $ git branch -b stable-website
$ hc-releases upload pkg/dist $ git push -f origin stable-website
``` ```
1. Publish the new index files to the releases site:
```
$ hc-releases publish
```
1. Update `website/config.rb` to point to the latest version, commit, and push.
1. Tell HashiBot to deploy in `#deploys`
```
hashibot deploy vagrant
```
1. Update `version.txt` to append `.dev` and add a new blank entry in the 1. Update `version.txt` to append `.dev` and add a new blank entry in the
CHANGELOG, commit, and push. CHANGELOG, commit, and push.