SpringCloud/spring-cloud-release-tools
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Added the ability to run a single step without skipping

Browse Source 
fixes #9
This commit is contained in:
Marcin Grzejszczak
2017-04-20 14:51:46 +02:00
parent 42024e1a2b
commit 2131efcdc4
6 changed files with 284 additions and 82 deletions
Download Patch File Download Diff File Expand all files Collapse all files

32
docs/src/main/asciidoc/spring-cloud-release-tools.adoc
View File

@@ -48,6 +48,32 @@ The application will start running from your working directory.
TIP: It is important that you clone the repository you are going to release using SSH in order for the
`releaser` to be able to push tags and commit changes automatically.
You will see text similar to this one
[source]
----
=== WHAT DO YOU WANT TO DO? ===
0) Perform a full release of this project without interruptions
1) Perform a full release of this project in a verbose mode (you'll be asked about skipping steps)
2) Update poms with versions from Spring Cloud Release
3) Build the project
4) Commit, tag and push the tag
5) Deploy the artifacts to Artifactory
6) Publish the docs
7) Go back to snapshots and bump originalVersion by patch
8) Push the commits
9) Close the milestone at Github
10) Create email / tweet etc. templates
You can press 'q' to quit
----
Just pick a number and continue! Pick either a full release or single steps.
TIP: Read before picking a number cause it might have changed between tool releases ;)
=== Project options
- `releaser.fixed-versions` - A String to String mapping of manually set versions. E.g. `"spring-cloud-cli" -> "1.0.0.RELEASE"` will set
@@ -78,11 +104,13 @@ folder and run your application like this:
[source,bash]
----
$ mkdir -p target
$ wget http://repo.spring.io/libs-milestone/org/springframework/cloud/internal/spring-cloud-release-tools-spring/1.0.0.M1/spring-cloud-release-tools-spring-1.0.0.M1.jar -O target/spring-cloud-release-tools-spring-1.0.0.M1.jar
$ wget http://repo.spring.io/libs-milestone/org/springframework/cloud/internal/spring-cloud-release-tools-spring/1.0.0.M1/spring-cloud-release-tools-spring-1.0.0.M1.jar -O ../spring-cloud-release-tools-spring-1.0.0.M1.jar
$ java -jar target/spring-cloud-release-tools-spring-1.0.0.M1.jar --spring.config.name=releaser
----
TIP: Notice that we're downloading the jar to a parent folder, not to `target`. That's because `target` get cleaned
during the build process
==== Specifying A Branch
By deafult the releaser will default to using the `master` branch of `spring-cloud-release`.