|
||||||||
|
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.
IMO this would be a very poor addition to the plugin.
There is only one special case where the user would benefit - at all other times, it would just be meaningless.
The only time that the files would match is - 1) if the jobs build on the master jenkins server and 2) the job has already been build at least once, and the workspace is still present.
Jobs are usually configured before they are executed.
If a user uses slaves, then this would always report an error.
The Source files pattern can use tokens to locate files eg $BUILD_NUMBER these would never resolve successfully at validation time.
Checking for the existence of files in a workspace when configuring a job is just a very bad idea.