[JIRA] [p4-plugin] (JENKINS-30353) Add perforce-plugin-style nodename hash to workspace environment variables expansion
Title: Message Title
Paul "TBBle" Hampson commented on JENKINS-30353
Re: Add perforce-plugin-style nodename hash to workspace environment variables expansion
If anyone else hits this issue, we're working around it locally with the following Groovy script, run before the SCM as a 'Execute system Groovy script' step:
// Work around https://issues.jenkins-ci.org/browse/JENKINS-30353
import hudson.model.*
def pa = new ParametersAction([
new StringParameterValue("NODE_NAME_HASH", String.valueOf(Thread.currentThread().executable.getBuiltOn().hashCode()))
])
// add variable to current job
Thread.currentThread().executable.addAction(pa)
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [p4-plugin] (JENKINS-30353) Add perforce-plugin-style nodename hash to workspace environment variables expansion
Title: Message Title
Paul "TBBle" Hampson created an issue
Jenkins / JENKINS-30353
Add perforce-plugin-style nodename hash to workspace environment variables expansion
Issue Type:
New Feature
Assignee:
Unassigned
Components:
p4-plugin
Created:
09/Sep/15 6:21 AM
Environment:
p4-plugin 1.3.0
Priority:
Minor
Reporter:
Paul "TBBle" Hampson
The perforce-plugin supported four custom tokens when generating per-slave client names from a base name:
Supported tokens are:
${basename} - The client name as configured in the above section
${hostname} - The hostname of the slave
${nodename} - The name of the slave in the CI server. Use this with caution.
