|
||||||||
|
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.
I had some trouble with the directory structure too, as there are jobs that copy their build results to another jobs workspace. This is done to be able to reuse the results for deployment even if another build is currently running.
I know there may be other and better solutions but one is not always able to change all legacy scripts at once, so that caused a lot of unnessesary problems.
I think the slave should mirror the master behavior as much as possible and so use the structure configured in the jenkins global configuration that sogabe pointed to.