sap-jenkins-library/documentation/docs/steps/cloudFoundryDeploy.md

${docGenStepName}

${docGenDescription}

Additional Hints

Deployment can be done

• in a standard way
• in a zero-downtime manner (using a blue-green deployment approach)

!!! note "Deployment supports multiple deployment tools" Currently the following are supported:

* Standard `cf push` and [Bluemix blue-green plugin](https://github.com/bluemixgaragelondon/cf-blue-green-deploy#how-to-use)
* [MTA CF CLI Plugin](https://github.com/cloudfoundry-incubator/multiapps-cli-plugin)

!!! note "Blue-Green Deployment with MTA CF CLI Plugin" The Multiapps Plugin offers 2 different strategies:

* [Blue-Green Deployment Strategy](https://github.com/SAP-samples/cf-mta-examples/tree/main/blue-green-deploy-strategy) - where the production environments are called “live” and “idle” during deployment. This strategy is activated with `mtaDeployParameters: --strategy blue-green --skip-testing-phase` and `deployType=standard`. After deployment, appnames are not appeneded by any suffix like `-live` or `-idle`.
* [Legacy Blue-Green Deployment](https://github.com/SAP-samples/cf-mta-examples/tree/main/blue-green-deploy-legacy) - where the productive environments are called “blue” and “green. Activated by `deployType=blue-green`. After deployment, appnames are appeneded by suffix like `-blue` or `-green`

!!! note Due to an incompatible change in the Cloud Foundry CLI, multiple buildpacks are not supported by this step. If your application contains a list of buildpacks instead of a single buildpack, this will be automatically re-written by the step when blue-green deployment is used.

!!! note Cloud Foundry supports the deployment of multiple applications using a single manifest file. This option is supported with project "Piper". In this case, define appName: '' since the app name for the individual applications has to be defined via the manifest. You can find details in the Cloud Foundry Documentation

Prerequisites

• Cloud Foundry organization, space and deployment users are available
• Credentials for deployment have been configured in Jenkins or Vault.

${docGenParameters}

${docGenConfiguration}