anchor.diff:  $ java -jar target/spring-cloud-release-tools-spring-1.0.0.M1.jar --releaser.working-dir=/path/to/project/root
   ----
   
  -=== Performing a release via Jenkins
  -
  -NOTE: Whenever a release process is broken, Jenkins will mark it with a red ball and break the build. Whenever a post-release action went wrong, but the release is successful, Jenkins will mark the build with a yellow ball and mark the build as unstable.
  -
  -==== Releasing a single project
  +=== Releasing through Jenkins
  +
  +NOTE: Whenever a release process is broken, Jenkins marks it with a red ball and breaks the build. Whenever a post-release action went wrong but the release is successful, Jenkins marks the build with a yellow ball and marks the build as unstable.
  +
  +==== Releasing a Single Project
   
   Let us assume that we are to release `spring-cloud-build` project. We need to do the following steps:
   
  -- create a branch (e.g. `springCloudBuildRelease`) in a BOM containing project e.g. https://github.com/spring-cloud/spring-cloud-release/[spring-cloud-release]
  +. Create a branch (for example, `springCloudBuildRelease`) in a project that contains a BOM (for example, https://github.com/spring-cloud/spring-cloud-release/[spring-cloud-release]). The following example shows how to do so:
   ```bash
   $ git clone git@github.com:spring-cloud/spring-cloud-release.git
   $ cd spring-cloud-release
   $ git checkout -b springCloudBuildRelease
   ```
  -- update *all* versions as if you were doing a release train. We need to update the project's versions, Boot version and dependencies versions too. Let us assume that we will eventually be doing a release train `Hoxton.M1` release, Spring Boot to latest available one and `spring-cloud-commons` to `1.2.3.BUILD-SNAPSHOT`
  +. Update *all* versions as if you were doing a release train. We need to update the project's versions, Boot version, and dependencies versions, too. Let us assume that we will eventually be doing a release train for the `Hoxton.M1` release, Spring Boot to the latest available one, and `spring-cloud-commons` to `1.2.3.BUILD-SNAPSHOT`. The following example shows how to do so:
   ```bash
   // setting the release train value
   $ ./mvnw versions:set -DnewVersion=Hoxton.M1 -DgenerateBackupPoms=false -DprocessAllModules=true
  
positive.code: 	... 31 common frames omitted
  ----
  
  To fix that just call
  
  [source,bash]
  ----
  
negative.code: // Setting the necessary dependencies
  $ ./mvnw versions:set-property -Dproperty=spring-cloud-commons.version -DnewVersion=1.2.3.BUILD-SNAPSHOT -pl spring-cloud-dependencies -DgenerateBackupPoms=false
  // NOTE!!!
  // Verify that the versions set by Maven are correct!!
  $ git diff
  // commit and push the branch
  $ git add . && git commit -m "Updating project for Spring Cloud Build release" && git push origin springCloudBuildRelease
  ```
  
  Since the project is prepared, go to Jenkins and select the https://jenkins.spring.io/view/Spring%20Cloud/view/Releaser/[Releaser view], which the following image shows:
  
  image::{github-raw}/docs/src/main/asciidoc/images/releasers.png[Releaser view]
  
  . Pick the proper releaser project (for example, `spring-cloud-build-releaser`). The following image shows the settings for this example:
  
  image::{github-raw}/docs/src/main/asciidoc/images/scBuildReleaser.png[Spring Cloud Build Releaser - build with parameters]
  
  . Next, click `Build with parameters`. The following image shows the UI for doing so:
  
  image::{github-raw}/docs/src/main/asciidoc/images/runningScBuildReleaser.png[Updated `RELEASER_POM_BRANCH`]
  
  Pick from which branch you would like the project (for example, `spring-cloud-build` - defaults to `master`) to be built and update the `RELEASER_POM_BRANCH` to point to the checked-out branch of Spring Cloud Release (for example, `springCloudBuildRelease`). You can pick whether you want to perform only post-release tasks or the whole release.
  
  . Finally, click `Build`.
  
  You are done!
  
  As a post action, do not forget to remove the branch. The following example shows how to do so:
  
  ```bash
  // to synchronize any deleted branches (don't run this if you want leave any deleted branches that were deleted in the origin)
  