[JIRA] (JENKINS-54472) Pin build at Perforce Label does not support variable expansion

[kwi...@perforce.com (JIRA)]

Title: Message Title

Karl Wirth commented on JENKINS-54472   Re: Pin build at Perforce Label does not support variable expansion Hi John Rocha - Have you tried this on P4-Plugin 10.1.3? For us the label expansion works. For example my variable is defined as 'SV_P4_CHANGELOG' in the job and I set the parameter to 'karl_label' when I manually ran the build:   Started by user unknown or anonymous Running as SYSTEM [EnvInject] - Loading node environment variables. Building on master in workspace /var/lib/jenkins/workspace/JENKINS-54472-PinBuildFreestyle ... p4 client -o jenkins-master-JENKINS-54472-PinBuildFreestyle-7 +... p4 info +... p4 info +... p4 client -o jenkins-master-JENKINS-54472-PinBuildFreestyle-7 +... p4 counter change +... p4 changes -m1 -ssubmitted //jenkins-master-JENKINS-54472-PinBuildFreestyle-7/... +... p4 label -o karl_label +... p4 label -o karl_label This also was the behavior we saw with pipeline.   However it is important to note that P4-Plugin can only sync to automatic labels. This is due to a limitation in Jenkins. This does not seem to be documented so I have created JENKINS-59526.   Add Comment   This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195237.1541443420000.5156.1569424200702%40Atlassian.JIRA.