You've already forked sap-jenkins-library
mirror of
https://github.com/SAP/jenkins-library.git
synced 2025-07-17 01:42:43 +02:00
fix(docu): cloudFoundryDeploy remove dead link (#5284)
This commit is contained in:
@ -44,7 +44,7 @@ This table compares deployment strategies for MTA and Non-MTA applications.
|
|||||||
This option is supported with project "Piper".
|
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.
|
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](https://docs.cloudfoundry.org/devguide/deploy-apps/manifest.html#multi-apps)
|
You can find details in the [Cloud Foundry Documentation](https://docs.cloudfoundry.org/devguide/deploy-apps/manifest.html#multi-apps)
|
||||||
- Recommended way to do **docker image deployments** is via [Kubernetes Piper step](https://github.wdf.sap.corp/pages/ContinuousDelivery/piper-doc/steps/kubernetesDeploy/).This step is not capable of deploying docker images built in the same pipeline using other piper steps[i.e., kanikoExecute].
|
- Recommended way to do **docker image deployments** is via kubernetesDeploy Piper step.This step is not capable of deploying docker images built in the same pipeline using other piper steps[i.e., kanikoExecute].
|
||||||
|
|
||||||
## Prerequisites
|
## Prerequisites
|
||||||
|
|
||||||
|
Reference in New Issue
Block a user