Spring/spring-data-dev-tools
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

#114 - Documented required permissions for Sagan GitHub token.

Browse Source
This commit is contained in:
Oliver Drotbohm
2019-04-02 12:41:53 +02:00
parent 594ca16875
commit 7d11a33642
2 changed files with 8 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
release-tools/application-local.template
View File

@@ -21,4 +21,8 @@ jira.url=https://jira.spring.io
# GPG
deployment.gpg.keyname=
deployment.gpg.password=
# deployment.gpg.executable=/usr/local/bin/gpg2
# deployment.gpg.executable=/usr/local/bin/gpg2
# A GitHub token with user:email, read:user and read:org scopes.
# User needs to be part of the Spring team on GitHub as well.
sagan.key=

4
release-tools/readme.md
View File

@@ -15,6 +15,8 @@
- `deployment.api-key` - The API key to use for artifact promotion.
- `deployment.password` - The password of the deployment user (buildmaster).
See `application-local.template` for details.
3. Run `mvn package appassembler:assemble && sh target/appassembler/bin/spring-data-release-shell`
4. Pre-release checks
@@ -52,6 +54,6 @@ $ tracker create releasetickets $trainIteration.next
$ tracker archive $trainIteration.previous
```
* Update versions in Sagan with `$ sagan update $releasetrains`.
* Update versions in Sagan with `$ sagan update $releasetrains`.
* Announce release (Blog, Twitter) and notify downstream dependency projects as needed. Dev-tools can assist you with `$ announcement $trainIteration`. Make sure to remove the changelog link to Envers as this module has no changelog.