|
||||||||
|
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/groups/opt_out.
We have a large list of projects (with role strategy plugin which makes assigns a LDAP role to projects with a certain prefix):
For those project groups I now want to create an admin job for each prefix:
Those admin jobs share the same System Groovy script CreateBranchJobFromTrunk.groovy, which clones a job and modifies the Subversion URL and the Sonar branch name.
The admin job is configured to have an Extensible Choice Parameter system Groovy script provider. The system Groovy script collects all jobs with the same prefix as the admin job itself and with a "trunk" suffix. For example: The "prefix1-admin-create-branch-job" collects the two projects "prefix1-projA-trunk" and "prefix1-projB-trunk".
Having the job name available in the System Groovy List Provider we could just clone the "prefix1-admin-create-branch-job" for new prefixes "prefix3" ... "prefixN" without having to worry that the prefix does not match.