jenkins/sap-jenkins-library
1
0
Fork 0
mirror of https://github.com/SAP/jenkins-library.git synced 2025-01-18 05:18:24 +02:00
Code Issues Releases Activity

cloudFoundryDeploy - fix stashing behavior (#396)

Browse Source 
This change fixes an error which only occurs in a Kubernetes landscape.
When initial stashes are filled, the deployment will fail since it misses the artifact to be deployed.

When providing an empty stash as default, Docker execution on Kubernetes will respect all content in the current workspace.
This commit is contained in:
Oliver Nocon 2018-11-27 16:02:06 +01:00 committed by GitHub
parent 32e20a7293
commit d1d07f241d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
vars/cloudFoundryDeploy.groovy
View File

@ -58,7 +58,10 @@ void call(Map parameters = [:]) {
echo "[${STEP_NAME}] General parameters: deployTool=${config.deployTool}, deployType=${config.deployType}, cfApiEndpoint=${config.cloudFoundry.apiEndpoint}, cfOrg=${config.cloudFoundry.org}, cfSpace=${config.cloudFoundry.space}, cfCredentialsId=${config.cloudFoundry.credentialsId}, deployUser=${config.deployUser}"
config.stashContent = utils.unstashAll(config.stashContent)
//make sure that all relevant descriptors, are available in workspace
utils.unstashAll(config.stashContent)
//make sure that for further execution whole workspace, e.g. also downloaded artifacts are considered
config.stashContent = [:]
if (config.deployTool == 'mtaDeployPlugin') {
// set default mtar path