[JIRA] (JENKINS-54286) Unable to use variable tokens as build property values in Create Package in Declarative Script

[jstarb...@scisolutions.com (JIRA)]

Title: Message Title

Jon Starbird commented on JENKINS-54286   Re: Unable to use variable tokens as build property values in Create Package in Declarative Script Not working for me, maybe the format isn't right. I tried it with double quotes around the variables as well as the original method of triple single quotes and neither worked. Build_Number and Job_Name are both environment variables but the gitprops.gitversion_fullsemver is from importing the gitversion properties into the job earlier. I do use it elsewhere  just fine even here for the ReleaseNumber. Here is what I have currently: buildMasterWithApplicationRelease(applicationId: "${env.BuildMaster_appId}", deployableId: "${env.BuildMaster_deployableId}") { script { BUILDMASTER_PACKAGE_NUMBER = buildMasterCreatePackage applicationId: BUILDMASTER_APPLICATION_ID, deployToFirstStage: true, packageNumber: BUILDMASTER_PACKAGE_NUMBER, releaseNumber: "${gitprops.GitVersion_MajorMinorPatch}", setBuildVariables: [ preserveVariables: false, variables: "JenkinsBuildNumber=$BUILD_NUMBER\nBuildVersion=$gitprops.GitVersion_FullSemVer\nJenkinsProject=$JOB_NAME"], waitTillBuildCompleted: [printLogOnFailure: false] } }  When it runs I get no errors on the Jenkins but on the BuildMaster it fails and doesn't show any values for the passed variables. Add Comment   This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.