|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
Yes, you are right, when using "export-params" you need to be careful about which jobs write to which parameter files and when, and which jobs uses which parameter files and when.
But, as I see it, this is already the case with the current implementation. If you e.g. only have 1 server running your "master" with a number of executors, you need to be careful about using parameter files. Your example with job A, B, and C which uses "/path/to/same/file" would be exactly the same, just all located on "master", and you would need to setup the parameter files so that they do not cause a conflict. Same if you e.g. have a "linux" slave, then all jobs running on that slave using parameter files need to be setup properly to not cause a conflict.
In my perspective, adding an option to allow exporting parameter files to the "master" does not introduce any new leak or weakness, it only adds new possibilities. The requirement will still be the same: You need to setup the parameter files so that they do not cause a conflict between jobs.