Skip to content
This repository has been archived by the owner on Feb 16, 2021. It is now read-only.

Commit

Permalink
Update dev readme and fix release process (#51)
Browse files Browse the repository at this point in the history
* Add project to evergreen command

* Fix typo in workdir in evergreen config
  • Loading branch information
BenElgar committed Aug 22, 2019
1 parent 35de342 commit e69ae35
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 3 deletions.
4 changes: 2 additions & 2 deletions .evergreen.yaml
Original file line number Diff line number Diff line change
@@ -1,3 +1,4 @@
---
functions:
"fetch_source":
- command: git.get_project
Expand Down Expand Up @@ -131,8 +132,7 @@ functions:
ARTIFACTS_ATTACH=$(ls artifacts | xargs -I {} echo "--attach artifacts/{} ")
export ARTIFACTS_ATTACH
${workingdir}/bin/hub release create --message "Atlas Service Broker ${version}" $ARTIFACTS_ATTACH v${version}
${workdir}/bin/hub release create --message "Atlas Service Broker ${version}" $ARTIFACTS_ATTACH v${version}
"setup_docker":
- command: shell.exec
params:
Expand Down
2 changes: 1 addition & 1 deletion dev/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ The release process consists of publishing a new Github release with attached bi

1. Add a new annotated tag using `git tag -a vX.X.X`. Git will prompt for a message which later will be used for the Github release message.
2. Push the tag using `git push <remote> vX.X.X`.
3. Run `evergreen patch --variants release --tasks all -y -f` and Evergreen will automatically complete the release.
3. Run `evergreen patch -p atlas-service-broker --variants release --tasks all -y -f` and Evergreen will automatically complete the release.

## Adding third-party dependencies

Expand Down

0 comments on commit e69ae35

Please sign in to comment.