|
||||||||
|
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.
Hi Gregory, not exactly. Our scenario is: we want to define the location in one place, and reference it from the other. Right now we have it as a Parameter, and also as an FSTrigger setting.
I understand that job Parameters cannot be used here – the question now is: is there any mechanism to avoid having this information hard-coded in two locations?
The FSTrigger is to a completion file that the build writes when it is done; we also want to do a directory of that for forensics, so we know time/date and size etc. The location is a complex path with the "branch" as a component of the path. We create new build jobs for new branches, and it would be far preferable to have to update one piece of data with the new branch, rather than needing to update two.
Is there any possibility that some other functionality might assist us here?
Thanks!
Ken