1
0
mirror of https://github.com/SAP/jenkins-library.git synced 2024-12-14 11:03:09 +02:00
sap-jenkins-library/vars/cloudFoundryDeploy.groovy
Daniel Kurzynski 63756dc81c
Fix cloudFoundryDeploy documentation (#2236)
Co-authored-by: Stephan Aßmus <stephan.assmus@sap.com>
2020-10-26 16:59:51 +01:00

676 lines
30 KiB
Groovy

import com.sap.piper.BashUtils
import com.sap.piper.CfManifestUtils
import com.sap.piper.ConfigurationHelper
import com.sap.piper.GenerateDocumentation
import com.sap.piper.JenkinsUtils
import com.sap.piper.Utils
import groovy.transform.Field
import static com.sap.piper.Prerequisites.checkScript
@Field String STEP_NAME = getClass().getName()
@Field Set GENERAL_CONFIG_KEYS = [
/**
* This is set in the common pipeline environment by the build tool, e.g. during the mtaBuild step.
*/
'buildTool',
'cloudFoundry',
/**
* Cloud Foundry API endpoint.
* @parentConfigKey cloudFoundry
*/
'apiEndpoint',
/**
* Defines the name of the application to be deployed to the Cloud Foundry space.
* @parentConfigKey cloudFoundry
*/
'appName',
/**
* Credentials to be used for deployment.
* @parentConfigKey cloudFoundry
*/
'credentialsId',
/**
* Defines the manifest to be used for deployment to Cloud Foundry.
* @parentConfigKey cloudFoundry
*/
'manifest',
/**
* Defines the manifest variables Yaml files to be used to replace variable references in manifest. This parameter
* is optional and will default to `["manifest-variables.yml"]`. This can be used to set variable files like it
* is provided by `cf push --vars-file <file>`.
*
* If the manifest is present and so are all variable files, a variable substitution will be triggered that uses
* the `cfManifestSubstituteVariables` step before deployment. The format of variable references follows the
* [Cloud Foundry standard](https://docs.cloudfoundry.org/devguide/deploy-apps/manifest-attributes.html#variable-substitution).
* @parentConfigKey cloudFoundry
*/
'manifestVariablesFiles',
/**
* Defines a `List` of variables as key-value `Map` objects used for variable substitution within the file given by `manifest`.
* Defaults to an empty list, if not specified otherwise. This can be used to set variables like it is provided
* by `cf push --var key=value`.
*
* The order of the maps of variables given in the list is relevant in case there are conflicting variable names and values
* between maps contained within the list. In case of conflicts, the last specified map in the list will win.
*
* Though each map entry in the list can contain more than one key-value pair for variable substitution, it is recommended
* to stick to one entry per map, and rather declare more maps within the list. The reason is that
* if a map in the list contains more than one key-value entry, and the entries are conflicting, the
* conflict resolution behavior is undefined (since map entries have no sequence).
*
* Note: variables defined via `manifestVariables` always win over conflicting variables defined via any file given
* by `manifestVariablesFiles` - no matter what is declared before. This is the same behavior as can be
* observed when using `cf push --var` in combination with `cf push --vars-file`.
* @parentConfigKey cloudFoundry
*/
'manifestVariables',
/**
* Cloud Foundry target organization.
* @parentConfigKey cloudFoundry
*/
'org',
/**
* Cloud Foundry target space.
* @parentConfigKey cloudFoundry
*/
'space',
/**
* Defines the tool which should be used for deployment.
* If it is not set it will be inferred automatically based on the buildTool, i.e., for MTA projects `mtaDeployPlugin` will be used and `cf_native` for other types of projects.
* @possibleValues 'cf_native', 'mtaDeployPlugin'
*/
'deployTool',
/**
* Defines the type of deployment, either `standard` deployment which results in a system downtime or a zero-downtime `blue-green` deployment.
* If 'cf_native' as deployType and 'blue-green' as deployTool is used in combination, your manifest.yaml may only contain one application.
* If this application has the option 'no-route' active the deployType will be changed to 'standard'.
* @possibleValues 'standard', 'blue-green'
*/
'deployType',
/**
* In case of a `blue-green` deployment the old instance will be deleted by default. If this option is set to true the old instance will remain stopped in the Cloud Foundry space.
* @possibleValues true, false
*/
'keepOldInstance',
/** @see dockerExecute */
'dockerImage',
/** @see dockerExecute */
'dockerWorkspace',
/** @see dockerExecute */
'stashContent',
/**
* Additional parameters passed to cf native deployment command.
*/
'cfNativeDeployParameters',
/**
* Addition command line options for cf api command.
* No escaping/quoting is performed. Not recommanded for productive environments.
*/
'apiParameters',
/**
* Addition command line options for cf login command.
* No escaping/quoting is performed. Not recommanded for productive environments.
*/
'loginParameters',
/**
* Additional parameters passed to mta deployment command.
*/
'mtaDeployParameters',
/**
* Defines a map of credentials that need to be replaced in the `mtaExtensionDescriptor`.
* This map needs to be created as `value-to-be-replaced`:`id-of-a-credential-in-jenkins`
*/
'mtaExtensionCredentials',
/**
* Defines additional extension descriptor file for deployment with the mtaDeployPlugin.
*/
'mtaExtensionDescriptor',
/**
* Defines the path to *.mtar for deployment with the mtaDeployPlugin. If not specified, it will use the mta file created in mtaBuild or search for an mtar file in the workspace.
*/
'mtaPath',
/**
* Allows to specify a script which performs a check during blue-green deployment. The script gets the FQDN as parameter and returns `exit code 0` in case check returned `smokeTestStatusCode`.
* More details can be found [here](https://github.com/bluemixgaragelondon/cf-blue-green-deploy#how-to-use) <br /> Currently this option is only considered for deployTool `cf_native`.
*/
'smokeTestScript',
/**
* Expected status code returned by the check.
*/
'smokeTestStatusCode',
/**
* Provides more output. May reveal sensitive information.
* @possibleValues true, false
*/
'verbose',
/**
* Docker image deployments are supported (via manifest file in general)[https://docs.cloudfoundry.org/devguide/deploy-apps/manifest-attributes.html#docker].
* If no manifest is used, this parameter defines the image to be deployed. The specified name of the image is
* passed to the `--docker-image` parameter of the cf CLI and must adhere it's naming pattern (e.g. REPO/IMAGE:TAG).
* See (cf CLI documentation)[https://docs.cloudfoundry.org/devguide/deploy-apps/push-docker.html] for details.
*
* Note: The used Docker registry must be visible for the targeted Cloud Foundry instance.
*/
'deployDockerImage',
/**
* If the specified image in `deployDockerImage` is contained in a Docker registry, which requires authorization
* this defines the credentials to be used.
*/
'dockerCredentialsId',
/**
* Toggle to activate the new go-implementation of the step. Off by default.
* @possibleValues true, false
*/
'useGoStep',
]
@Field Set STEP_CONFIG_KEYS = GENERAL_CONFIG_KEYS
@Field Set PARAMETER_KEYS = STEP_CONFIG_KEYS
@Field Map CONFIG_KEY_COMPATIBILITY = [
cloudFoundry: [
apiEndpoint: 'cfApiEndpoint',
appName:'cfAppName',
credentialsId: 'cfCredentialsId',
manifest: 'cfManifest',
manifestVariablesFiles: 'cfManifestVariablesFiles',
manifestVariables: 'cfManifestVariables',
org: 'cfOrg',
space: 'cfSpace',
],
mtaExtensionDescriptor: 'cloudFoundry/mtaExtensionDescriptor'
]
/**
* Deploys an application to a test or production space within Cloud Foundry.
* Deployment can be done
*
* * in a standard way
* * in a zero downtime manner (using a [blue-green deployment approach](https://martinfowler.com/bliki/BlueGreenDeployment.html))
*
* !!! 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
* Due to [an incompatible change](https://github.com/cloudfoundry/cli/issues/1445) in the Cloud Foundry CLI, multiple buildpacks are not supported by this step.
* If your `application` contains a list of `buildpacks` instead 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 Piper.
*
* In this case define `appName: ''` since the app name for the individual applications have 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)
*/
@GenerateDocumentation
void call(Map parameters = [:]) {
handlePipelineStepErrors (stepName: STEP_NAME, stepParameters: parameters) {
final script = checkScript(this, parameters) ?: this
def utils = parameters.juStabUtils ?: new Utils()
def jenkinsUtils = parameters.jenkinsUtilsStub ?: new JenkinsUtils()
String stageName = parameters.stageName ?: env.STAGE_NAME
Map config = ConfigurationHelper.newInstance(this)
.loadStepDefaults([:], stageName)
.mixinGeneralConfig(script.commonPipelineEnvironment, GENERAL_CONFIG_KEYS, CONFIG_KEY_COMPATIBILITY)
.mixinStepConfig(script.commonPipelineEnvironment, STEP_CONFIG_KEYS, CONFIG_KEY_COMPATIBILITY)
.mixinStageConfig(script.commonPipelineEnvironment, stageName, STEP_CONFIG_KEYS, CONFIG_KEY_COMPATIBILITY)
.mixin(parameters, PARAMETER_KEYS, CONFIG_KEY_COMPATIBILITY)
.addIfEmpty('buildTool', script.commonPipelineEnvironment.getBuildTool())
.dependingOn('buildTool').mixin('deployTool')
.dependingOn('deployTool').mixin('dockerImage')
.dependingOn('deployTool').mixin('dockerWorkspace')
.withMandatoryProperty('cloudFoundry/org')
.withMandatoryProperty('cloudFoundry/space')
.withMandatoryProperty('cloudFoundry/credentialsId', null, {c -> return !c.containsKey('vaultAppRoleTokenCredentialsId') || !c.containsKey('vaultAppRoleSecretTokenCredentialsId')})
.use()
if (config.useGoStep == true) {
List credentials = [
[type: 'usernamePassword', id: 'cfCredentialsId', env: ['PIPER_username', 'PIPER_password']],
[type: 'usernamePassword', id: 'dockerCredentialsId', env: ['PIPER_dockerUsername', 'PIPER_dockerPassword']]
]
piperExecuteBin(parameters, STEP_NAME, 'metadata/cloudFoundryDeploy.yaml', credentials)
return
}
utils.pushToSWA([
step: STEP_NAME,
stepParamKey1: 'deployTool',
stepParam1: config.deployTool,
stepParamKey2: 'deployType',
stepParam2: config.deployType,
stepParamKey3: 'scriptMissing',
stepParam3: parameters?.script == null
], config)
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}"
//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 = []
// validate cf app name to avoid a failing deployment due to invalid chars
if (config.cloudFoundry.appName) {
String appName = config.cloudFoundry.appName.toString()
boolean isValidCfAppName = appName.matches("^[a-zA-Z0-9][a-zA-Z0-9\\-]*[a-zA-Z0-9]\$")
if (!isValidCfAppName) {
echo "WARNING: Your application name $appName contains non-alphanumeric characters which may lead to errors in the future, as they are not supported by CloudFoundry.\n" +
"For more details please visit https://docs.cloudfoundry.org/devguide/deploy-apps/deploy-app.html#basic-settings"
// Underscore in the app name will lead to errors because cf uses the appname as part of the url which may not contain underscores
if (appName.contains("_")) {
error("Your application name $appName contains a '_' (underscore) which is not allowed, only letters, dashes and numbers can be used. " +
"Please change the name to fit this requirement.\n" +
"For more details please visit https://docs.cloudfoundry.org/devguide/deploy-apps/deploy-app.html#basic-settings.")
}
if (appName.startsWith("-") || appName.endsWith("-")) {
error("Your application name $appName contains a starts or ends with a '-' (dash) which is not allowed, only letters, dashes and numbers can be used. " +
"Please change the name to fit this requirement.\n" +
"For more details please visit https://docs.cloudfoundry.org/devguide/deploy-apps/deploy-app.html#basic-settings.")
}
}
}
boolean deployTriggered = false
boolean deploySuccess = true
try {
if (config.deployTool == 'mtaDeployPlugin') {
deployTriggered = true
handleMTADeployment(config, script)
}
else if (config.deployTool == 'cf_native') {
deployTriggered = true
handleCFNativeDeployment(config, script)
}
else {
deployTriggered = false
echo "[${STEP_NAME}] WARNING! Found unsupported deployTool. Skipping deployment."
}
} catch (err) {
deploySuccess = false
throw err
} finally {
if (deployTriggered) {
reportToInflux(script, config, deploySuccess, jenkinsUtils)
}
}
}
}
private void handleMTADeployment(Map config, script) {
// set default mtar path
if(!config.mtaPath) {
config.mtaPath = script.commonPipelineEnvironment.mtarFilePath ?: findMtar()
}
dockerExecute(script: script, dockerImage: config.dockerImage, dockerWorkspace: config.dockerWorkspace, stashContent: config.stashContent) {
deployMta(config)
}
}
def findMtar(){
def mtarFiles = findFiles(glob: '**/*.mtar')
if(mtarFiles.length > 1){
error "[${STEP_NAME}] Found multiple *.mtar files, please specify file via mtaPath parameter! ${mtarFiles}"
}
if(mtarFiles.length == 1){
return mtarFiles[0].path
}
error "[${STEP_NAME}] No *.mtar file found!"
}
def deployMta(config) {
String mtaExtensionDescriptorParam = ''
if (config.mtaExtensionDescriptor) {
if (!fileExists(config.mtaExtensionDescriptor)) {
error "[${STEP_NAME}] The mta extension descriptor file ${config.mtaExtensionDescriptor} does not exist at the configured location."
}
mtaExtensionDescriptorParam = "-e ${config.mtaExtensionDescriptor}"
if (config.mtaExtensionCredentials) {
handleMtaExtensionCredentials(config)
}
}
def deployCommand = 'deploy'
if (config.deployType == 'blue-green') {
deployCommand = 'bg-deploy'
if (config.mtaDeployParameters.indexOf('--no-confirm') < 0) {
config.mtaDeployParameters += ' --no-confirm'
}
}
def deployStatement = "cf ${deployCommand} ${config.mtaPath} ${config.mtaDeployParameters} ${mtaExtensionDescriptorParam}"
def apiStatement = "cf api ${config.cloudFoundry.apiEndpoint} ${config.apiParameters}"
echo "[${STEP_NAME}] Deploying MTA (${config.mtaPath}) with following parameters: ${mtaExtensionDescriptorParam} ${config.mtaDeployParameters}"
try {
deploy(apiStatement, deployStatement, config, null)
} finally {
if (config.mtaExtensionCredentials && config.mtaExtensionDescriptor && fileExists(config.mtaExtensionDescriptor)) {
sh "mv --force ${config.mtaExtensionDescriptor}.original ${config.mtaExtensionDescriptor} || echo 'The file ${config.mtaExtensionDescriptor}.original could not be renamed.'"
}
}
}
private void handleMtaExtensionCredentials(Map<?, ?> config) {
echo "[${STEP_NAME}] Modifying ${config.mtaExtensionDescriptor}. Adding credential values from Jenkins."
sh "cp ${config.mtaExtensionDescriptor} ${config.mtaExtensionDescriptor}.original"
Map mtaExtensionCredentials = config.mtaExtensionCredentials
String fileContent = ''
try {
fileContent = readFile config.mtaExtensionDescriptor
} catch (Exception e) {
error("[${STEP_NAME}] Unable to read mta extension file ${config.mtaExtensionDescriptor}. (${e.getMessage()})")
}
mtaExtensionCredentials.each { key, credentialsId ->
withCredentials([string(credentialsId: credentialsId, variable: 'mtaExtensionCredential')]) {
fileContent = fileContent.replace('<%= ' + key.toString() + ' %>', mtaExtensionCredential.toString())
}
}
writeFile file: config.mtaExtensionDescriptor, text: fileContent
}
private checkAndUpdateDeployTypeForNotSupportedManifest(Map config){
String manifestFile = config.cloudFoundry.manifest ?: 'manifest.yml'
if(config.deployType == 'blue-green' && fileExists(manifestFile)){
Map manifest = readYaml file: manifestFile
List applications = manifest.applications
if(applications) {
if(applications.size()>1){
error "[${STEP_NAME}] Your manifest contains more than one application. For blue green deployments your manifest file may contain only one application."
}
if(applications.size==1 && applications[0]['no-route']){
echo '[WARNING] Blue green deployment is not possible for application without route. Using deployment type "standard" instead.'
config.deployType = 'standard'
}
}
}
}
private void handleCFNativeDeployment(Map config, script) {
config.smokeTest = ''
checkAndUpdateDeployTypeForNotSupportedManifest(config)
if (config.deployType == 'blue-green') {
prepareBlueGreenCfNativeDeploy(config, script)
} else {
prepareCfPushCfNativeDeploy(config)
}
echo "[${STEP_NAME}] CF native deployment (${config.deployType}) with:"
echo "[${STEP_NAME}] - cfAppName=${config.cloudFoundry.appName}"
echo "[${STEP_NAME}] - cfManifest=${config.cloudFoundry.manifest}"
echo "[${STEP_NAME}] - cfManifestVariables=${config.cloudFoundry.manifestVariables ?: 'none specified'}"
echo "[${STEP_NAME}] - cfManifestVariablesFiles=${config.cloudFoundry.manifestVariablesFiles ?: 'none specified'}"
echo "[${STEP_NAME}] - cfdeployDockerImage=${config.deployDockerImage ?: 'none specified'}"
echo "[${STEP_NAME}] - cfdockerCredentialsId=${config.dockerCredentialsId ?: 'none specified'}"
echo "[${STEP_NAME}] - smokeTestScript=${config.smokeTestScript}"
checkIfAppNameIsAvailable(config)
def dockerCredentials = []
if (config.dockerCredentialsId != null && config.dockerCredentialsId != '') {
dockerCredentials.add(usernamePassword(
credentialsId: config.dockerCredentialsId,
passwordVariable: 'dockerPassword',
usernameVariable: 'dockerUsername'
))
}
withCredentials(dockerCredentials) {
dockerExecute(
script: script,
dockerImage: config.dockerImage,
dockerWorkspace: config.dockerWorkspace,
stashContent: config.stashContent,
dockerEnvVars: [
CF_HOME : "${config.dockerWorkspace}",
CF_PLUGIN_HOME : "${config.dockerWorkspace}",
// if the Docker registry requires authentication the DOCKER_PASSWORD env variable must be set
CF_DOCKER_PASSWORD: "${dockerCredentials.isEmpty() ? '' : dockerPassword}",
STATUS_CODE : "${config.smokeTestStatusCode}"
]
) {
if(dockerCredentials.size() > 0) {
config.dockerUsername = dockerUsername
}
deployCfNative(config)
}
}
}
private prepareBlueGreenCfNativeDeploy(config,script) {
if (config.smokeTestScript == 'blueGreenCheckScript.sh') {
writeFile file: config.smokeTestScript, text: libraryResource(config.smokeTestScript)
}
if (config.smokeTestScript) {
config.smokeTest = '--smoke-test $(pwd)/' + config.smokeTestScript
sh "chmod +x ${config.smokeTestScript}"
}
config.deployCommand = 'blue-green-deploy'
cfManifestSubstituteVariables(
script: script,
manifestFile: config.cloudFoundry.manifest,
manifestVariablesFiles: config.cloudFoundry.manifestVariablesFiles,
manifestVariables: config.cloudFoundry.manifestVariables
)
handleLegacyCfManifest(config)
if (!config.keepOldInstance) {
config.deployOptions = '--delete-old-apps'
}
}
def handleLegacyCfManifest(config) {
def manifest = readYaml file: config.cloudFoundry.manifest
String originalManifest = manifest.toString()
manifest = CfManifestUtils.transform(manifest)
String transformedManifest = manifest.toString()
if (originalManifest != transformedManifest) {
echo """The file ${config.cloudFoundry.manifest} is not compatible with the Cloud Foundry blue-green deployment plugin. Re-writing inline.
See this issue if you are interested in the background: https://github.com/cloudfoundry/cli/issues/1445.\n
Original manifest file content: $originalManifest\n
Transformed manifest file content: $transformedManifest"""
sh "rm ${config.cloudFoundry.manifest}"
writeYaml file: config.cloudFoundry.manifest, data: manifest
}
}
private prepareCfPushCfNativeDeploy(config) {
config.deployCommand = 'push'
config.deployOptions = "${varOptions(config)}${varFileOptions(config)}"
}
private varOptions(Map config) {
String varPart = ''
if (config.cloudFoundry.manifestVariables) {
if (!(config.cloudFoundry.manifestVariables in List)) {
error "[${STEP_NAME}] ERROR: Parameter config.cloudFoundry.manifestVariables is not a List!"
}
config.cloudFoundry.manifestVariables.each {
if (!(it in Map)) {
error "[${STEP_NAME}] ERROR: Parameter config.cloudFoundry.manifestVariables.$it is not a Map!"
}
it.keySet().each { varKey ->
String varValue=BashUtils.quoteAndEscape(it.get(varKey).toString())
varPart += " --var $varKey=$varValue"
}
}
}
if (varPart) echo "We will add the following string to the cf push call:$varPart !"
return varPart
}
private String varFileOptions(Map config) {
String varFilePart = ''
if (config.cloudFoundry.manifestVariablesFiles) {
if (!(config.cloudFoundry.manifestVariablesFiles in List)) {
error "[${STEP_NAME}] ERROR: Parameter config.cloudFoundry.manifestVariablesFiles is not a List!"
}
config.cloudFoundry.manifestVariablesFiles.each {
if (fileExists(it)) {
varFilePart += " --vars-file ${BashUtils.quoteAndEscape(it)}"
} else {
echo "[${STEP_NAME}] [WARNING] We skip adding not-existing file '$it' as a vars-file to the cf create-service-push call"
}
}
}
if (varFilePart) echo "We will add the following string to the cf push call:$varFilePart !"
return varFilePart
}
private checkIfAppNameIsAvailable(config) {
if (config.cloudFoundry.appName == null || config.cloudFoundry.appName == '') {
if (config.deployType == 'blue-green') {
error "[${STEP_NAME}] ERROR: Blue-green plugin requires app name to be passed (see https://github.com/bluemixgaragelondon/cf-blue-green-deploy/issues/27)"
}
if (fileExists(config.cloudFoundry.manifest)) {
def manifest = readYaml file: config.cloudFoundry.manifest
if (!manifest || !manifest.applications || !manifest.applications[0].name) {
error "[${STEP_NAME}] ERROR: No appName available in manifest ${config.cloudFoundry.manifest}."
}
} else {
error "[${STEP_NAME}] ERROR: No manifest file ${config.cloudFoundry.manifest} found."
}
}
}
def deployCfNative(config) {
// the deployStatement is complex and has lot of options; using a list and findAll allows to put each option
// as a single list element; if a option is not set (= null or '') this removed before every element is joined
// via a single whitespace; results in a single line deploy statement
def deployStatement = [
'cf',
config.deployCommand,
config.cloudFoundry.appName,
config.deployOptions,
config.cloudFoundry.manifest ? "-f '${config.cloudFoundry.manifest}'" : null,
config.deployDockerImage && config.deployType != 'blue-green' ? "--docker-image ${config.deployDockerImage}" : null,
config.dockerUsername && config.deployType != 'blue-green' ? "--docker-username ${dockerUsername}" : null,
config.smokeTest,
config.cfNativeDeployParameters
].findAll { s -> s != null && s != '' }.join(" ")
deploy(null, deployStatement, config, { c -> stopOldAppIfRunning(c) })
}
private deploy(String cfApiStatement, String cfDeployStatement, config, Closure postDeployAction) {
withCredentials([usernamePassword(
credentialsId: config.cloudFoundry.credentialsId,
passwordVariable: 'password',
usernameVariable: 'username'
)]) {
def cfTraceFile = 'cf.log'
def deployScript = """#!/bin/bash
set +x
set -e
export HOME=${config.dockerWorkspace}
export CF_TRACE=${cfTraceFile}
${cfApiStatement ?: ''}
cf login -u \"${username}\" -p '${password}' -a ${config.cloudFoundry.apiEndpoint} -o \"${config.cloudFoundry.org}\" -s \"${config.cloudFoundry.space}\" ${config.loginParameters}
cf plugins
${cfDeployStatement}
"""
if (config.verbose) {
// Password contained in output below is hidden by withCredentials
echo "[INFO][${STEP_NAME}] Executing command: '${deployScript}'."
}
try {
sh deployScript
} catch (e) {
handleCfCliLog(cfTraceFile)
error "[${STEP_NAME}] ERROR: The execution of the deploy command failed, see the log for details."
}
if (config.verbose) {
handleCfCliLog(cfTraceFile)
}
if (postDeployAction) postDeployAction(config)
sh "cf logout"
}
}
private void handleCfCliLog(String logFile){
if(fileExists(file: logFile)) {
echo '### START OF CF CLI TRACE OUTPUT ###'
// Would be nice to inline the two next lines, but that is not understood by the test framework
def cfTrace = readFile(file: logFile)
echo cfTrace
echo '### END OF CF CLI TRACE OUTPUT ###'
} else {
echo "No trace file found at '${logFile}'"
}
}
private void stopOldAppIfRunning(Map config) {
String oldAppName = "${config.cloudFoundry.appName}-old"
String cfStopOutputFileName = "${UUID.randomUUID()}-cfStopOutput.txt"
if (config.keepOldInstance && config.deployType == 'blue-green') {
try {
sh "cf stop $oldAppName &> $cfStopOutputFileName"
} catch (e) {
String cfStopOutput = readFile(file: cfStopOutputFileName)
if (!cfStopOutput.contains("$oldAppName not found")) {
error "[${STEP_NAME}] ERROR: Could not stop application $oldAppName. Error: $cfStopOutput"
}
}
}
}
private void reportToInflux(script, config, deploySuccess, JenkinsUtils jenkinsUtils) {
def deployUser = ''
withCredentials([usernamePassword(
credentialsId: config.cloudFoundry.credentialsId,
passwordVariable: 'password',
usernameVariable: 'username'
)]) {
deployUser = username
}
def timeFinished = new Date().format( 'MMM dd, yyyy - HH:mm:ss' )
def triggerCause = jenkinsUtils.isJobStartedByUser()?'USER':(jenkinsUtils.isJobStartedByTimer()?'TIMER': 'OTHER')
def deploymentData = [deployment_data: [
artifactUrl: 'n/a', //might be added later on during pipeline run (written to commonPipelineEnvironment)
deployTime: timeFinished,
jobTrigger: triggerCause
]]
def deploymentDataTags = [deployment_data: [
artifactVersion: script.commonPipelineEnvironment.getArtifactVersion(),
deployUser: deployUser,
deployResult: deploySuccess?'SUCCESS':'FAILURE',
cfApiEndpoint: config.cloudFoundry.apiEndpoint,
cfOrg: config.cloudFoundry.org,
cfSpace: config.cloudFoundry.space,
]]
influxWriteData script: script, customData: [:], customDataTags: [:], customDataMap: deploymentData, customDataMapTags: deploymentDataTags
}