anchor.diff:  # to store the pass in the agent
   $ ssh-add ~/.ssh/id_rsa
   ----
  -
  -before running the app
  
positive.code: $ git add greenwich_sr2.properties && git commit -m "Added Greenwich.SR2 properties" && git push origin jenkins-releaser-config
  ```
  
  Since the project is prepared, go to Jenkins to the https://jenkins.spring.io/view/Spring%20Cloud/view/Releaser/[Releaser view].
  
  image::{github-raw}/docs/src/main/asciidoc/images/releasersForMetaRelease.png[Releaser view]
  
   Pick the proper meta-releaser project (e.g. `spring-cloud-meta-releaser`.
  
  image::{github-raw}/docs/src/main/asciidoc/images/springCloudMetaRelease.png[Spring Cloud Meta Releaser - build with parameters]
  
  Next, click `Build with parameters`.
  
  image::{github-raw}/docs/src/main/asciidoc/images/runningSpringCloudMetaReleaser.png[Spring Cloud Meta Releaser view]
  
  You have quite a few options to pick, but the most important one is to set the value of the `RELEASE_VERSION` to the given release train version (e.g. `Greenwich.SR2`). Continue updating the rest of the fields if necessary and read the field descriptions and this documentation for more information.
  
  Finally, click `Build`.
  
  You're done!
  
  === FAQ
  
  ==== JSchException: Auth fail
  
  I got such an exception
  
  [source]
  ----
  
negative.code: $ git push origin --delete springCloudBuildRelease
  ```
  
  ==== Releasing a Release Train
  
  We call a release train a `meta-release`. In order to perform one, you need to:
  
  . In your project (which must contain a BOM, such as `spring-cloud-release`) you have to have a branch, where you store properties with versions of your projects. For example, the branch name can be https://github.com/spring-cloud/spring-cloud-release/tree/jenkins-releaser-config[jenkins-releaser-config]). The folloiwng example shows how to do so:
  ```bash
  $ git clone git@github.com:spring-cloud/spring-cloud-release.git
  $ cd spring-cloud-release
  $ git checkout jenkins-releaser-config
  ```
  . Create a file that contains all properties for a given release train. The name of the release train should be lowercase, and dots should be converted to underscores. For example, for the `Greenwich.SR2` release train we need to have a file named  `greenwich_sr2.properties`. The following example shows how to do so:
  ```bash
  $ touch greenwich_sr2.properties
  ```
  . We need to update the file with all versions for the release train. The properties file contains an *ordered* list of `releaser.fixed-versions[project-name]=project-version` entries, as the following listing shows:
  ```bash
  $ echo "releaser.fixed-versions[spring-boot]=2.1.5.RELEASE
  releaser.fixed-versions[spring-cloud-build]=2.1.5.RELEASE
  