[JIRA] (JENKINS-54472) Pin build at Perforce Label does not support variable expansion
Title: Message Title Karl Wirth closed an issue as Done John has provided a workaround. Jenkins / JENKINS-54472 Pin build at Perforce Label does not support variable expansion Change By: Karl Wirth Status: Open Closed Resolution: Done 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.
[JIRA] (JENKINS-54472) Pin build at Perforce Label does not support variable expansion
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-54472 Pin build at Perforce Label does not support variable expansion Change By: Karl Wirth Labels: P4_B P4_SUPPORT 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.154144342.1623.1577970060750%40Atlassian.JIRA.
[JIRA] (JENKINS-54472) Pin build at Perforce Label does not support variable expansion
Title: Message Title
John Rocha commented on JENKINS-54472
Re: Pin build at Perforce Label does not support variable expansion
Hello Karl Wirth, I was able to get this to work with plugin 1.10.5 (I haven't tried for awhile, so it may work with earlier versions too). What I did was as follows:
Define a choice parameter: P4_LABEL, with string trimming enabled.
Set the Perforce field "Pin build at Perforce Label" to ${P4_LABEL}
With this I successfully synced to change set 34307 by entering a value of @34307. Moreover, if I enter nothing, using the default where P4_LABEL is now set to nothing, it correctly pulls latest as expected. I think this case can be closed. I don't know if there was a fix that went in from when I first reported or if it was a miss-configuration on my part... but it works now when I do as explained above.
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.154144342.10076.1571356740150%40Atlassian.JIRA.
[JIRA] (JENKINS-54472) Pin build at Perforce Label does not support variable expansion
Title: Message Title Karl Wirth commented on JENKINS-54472 Re: Pin build at Perforce Label does not support variable expansion Correct label behavior is not described. 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.154144342.5159.1569424380136%40Atlassian.JIRA.
[JIRA] (JENKINS-54472) Pin build at Perforce Label does not support variable expansion
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 ema
[JIRA] (JENKINS-54472) Pin build at Perforce Label does not support variable expansion
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-54472 Pin build at Perforce Label does not support variable expansion Change By: Karl Wirth Labels: P4_B P4_SUPPORT 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.154144342.4856.1569404700316%40Atlassian.JIRA.
[JIRA] (JENKINS-54472) Pin build at Perforce Label does not support variable expansion
Title: Message Title Karl Wirth assigned an issue to Karl Wirth Jenkins / JENKINS-54472 Pin build at Perforce Label does not support variable expansion Change By: Karl Wirth Assignee: Charusheela Bopardikar Karl Wirth 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.154144342.4853.1569404641821%40Atlassian.JIRA.
[JIRA] (JENKINS-54472) Pin build at Perforce Label does not support variable expansion
Title: Message Title Charusheela Bopardikar commented on JENKINS-54472 Re: Pin build at Perforce Label does not support variable expansion Your comment is acknowledged. Will update here as soon as any progress is made. 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.154144342.2911.1569234840326%40Atlassian.JIRA.
[JIRA] (JENKINS-54472) Pin build at Perforce Label does not support variable expansion
Title: Message Title John Rocha commented on JENKINS-54472 Re: Pin build at Perforce Label does not support variable expansion Any update on this issue? 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.154144342.5486.1568738820098%40Atlassian.JIRA.
[JIRA] (JENKINS-54472) Pin build at Perforce Label does not support variable expansion
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-54472 Pin build at Perforce Label does not support variable expansion Change By: Paul Allen Labels: P4_PLUGIN p4 p4plugin P4_B 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.
[JIRA] (JENKINS-54472) Pin build at Perforce Label does not support variable expansion
Title: Message Title Paul Allen assigned an issue to Charusheela Bopardikar Jenkins / JENKINS-54472 Pin build at Perforce Label does not support variable expansion Change By: Paul Allen Assignee: Charusheela Bopardikar 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.
[JIRA] (JENKINS-54472) Pin build at Perforce Label does not support variable expansion
Title: Message Title
John Rocha created an issue
Jenkins / JENKINS-54472
Pin build at Perforce Label does not support variable expansion
Issue Type:
Bug
Assignee:
Unassigned
Components:
p4-plugin
Created:
2018-11-05 18:43
Environment:
CentOS-7 (Linux CentOS-7 3.10.0-862.14.4.el7.x86_64 #1 SMP Wed Sep 26 15:12:11 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux) Jenkins war (org.jenkins-ci.main:jenkins-war:2.138.2) P4 Plugin (1.9.3)
Labels:
p4 p4plugin P4_PLUGIN
Priority:
Major
Reporter:
John Rocha
The description for the "Pin a build at Perforce Label" indicates the following:
When a build is triggered by Polling, Build Now or an external Action, the workspace will sync only to the specified label. Any other specified change or label will be ignored.
Supports variable expansion e.g. ${VAR}. If 'now' is used, or a variable that expands to 'now', then the latest change is used (within the scope of the workspace view).
This is not working. I tried ${SV_P4_CHANGELOG} where the value was not set, and hence is empty, and the tool is looking for the label SV_P4_CHANGELOG, as shown below
