Our builds are typically parameterized with a "branch" to build against.
The client specs used by our nodes are already using a <nodename>_<branch>
naming convention. I would like to use this format for the slave client
names in the peforce plugin.
The only 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.
${hash} - The hash code of the slave name
Because of this limitation, our underlying builds handle syncing, but I
would really like to start using the perforce plugin to take advantage of
the Jenkins features related to SCM.
Would it be difficult to support additional tokens in this field? Or is
this task relatively easy for someone without any Jenkins plugin
development experience?
Thanks,
Stuart
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
