|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
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.
When a job start there is a variable ${EXECUTOR_NUMBER} that indicated the current executor that is going to perform the work.
https://wiki.jenkins-ci.org/display/JENKINS/Building+a+software+project
Since we know ${EXECUTOR_NUMBER} when a job starts, any reason we can't can set the workspace and client spec dynamically ?
When you run a multiple instances of a job in Jenkins the default behaviour is to add a @n (etc @2 for the 2nd executor), automatically to the workspace (and p4 client spec)
So Jenkins already handles different workspaces for different executors.