anchor.diff:  * `CLIENT_SECRET`
   * `TOKEN_SECRET`
   
  -=== Manual Deployment with Gradle
  +=== Manual Deployment with Cloud Foundry CLI
   
  -Manual deployment with Gradle can be performed by invoking Gradle directly from the command line:
  +Manual deployment with https://docs.cloudfoundry.org/cf-cli/[Cloud Foundry CLI] can be done after https://docs.cloudfoundry.org/cf-cli/use-cli-plugins.html#plugin-install[installing it].
  +
  +First log into Cloud Foundry.
  +For example:
   
   [source,bash]
   ----
  -$ ./gradlew assemble deploy -Pspace=<space>
  +$ cf login -a api.run.pivotal.io -o pivotal-cla -s production -u $CF_USERNAME -p $CF_PASSWORD
   ----
   
  -The manual deployment with Gradle defaults to pivotal as organization and requires `space` to be provided.
  -It activates the `cloudfoundry` profile which requires a MySQL database and a Redis instance.
  -
  -=== Manual Deployment with `cf push`
  -
  -You can deploy `pivotal-cla` using `cf push`. This mode is isolated from any organization and space preferences.
  +Pushing to Cloud Foundry activates the `cloudfoundry` profile which requires a MySQL database and a Redis instance.
  +You can perform a zero-downtime deploy to Cloud Foundry using the included cf-push.sh script.
  +For example:
   
   [source,bash]
   ----
  -$ cf push -p build/libs/pivotal-cla-<version>.jar
  +$ ./ci/scripts/cf-push.sh pivotal-cla-production $CLIENT_ID $CLIENT_SECRET $TOKEN_SECRET $TRAVIS_BUILD_NUMBER-$TRAVIS_COMMIT
   ----
  +
   
   == Profiles
   
  
positive.code: * `security.oauth2.pivotal-cla.tokenSecret`: A Personal Access Token with public_repo scope
  * For manual deployment only: `space`: Name of the space
  
  === Variants (aka. Blue/Green-Deployment)
  
  Production and Staging have blue/green deployment set up. That's done by setting the `variants` property of the http://docs.run.pivotal.io/buildpacks/java/build-tool-int.html#gradle[Cloud Foundry Gradle plugin].
  Setting `variants` causes `cfDeploy` to check which variant is active and deploy to the inactive variant. The deployment
  task switches blue/green instances using `cfSwapDeployed` once the application is deployed and started.
  
  To recover from a failed swapping or deployment, it's required to unmap application routes and re-trigger deployment.
  
  === TravisCI
  
  TravisCI builds for the `master` branch get deployed to production. Builds for branches starting with `staging-` get deployed to the staging space.
  The build is set up to provide deployment properties as environment variables:
  
  * `CF_USERNAME`
  
negative.code: 
  == Cloud Foundry
  
  Deploying the application to Cloud Foundry can be performed using the https://docs.cloudfoundry.org/cf-cli/[Cloud Foundry CLI].
  It's set up for TravisCI and manual deployment mode.
  
  === Required Properties
  