|
||||||||
|
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/d/optout.
Our cleaning scripts do work reasonably well, but like all code they can get broken and they do change frequently so breakages are statistically probable. They are fine for devs to rely on locally, but I wouldn't be happy to solely rely on them for important client builds and not for an overnight clean where we want to ensure everything is reset.
Templates are an interesting idea, not something I have really used so far. I'll have a closer look for future use. Thanks Rob.
The client isn't reused. The branch name variable is already part of the client name which Jenkins creates so client workspaces are unique per branch. I agree, it would be bad practice to do otherwise.
We are happy with the solution we have at the moment. It is very flexible with branches, reliable and very little work to maintain. The only issue I encountered with setting it up was the problem with custom workspaces which I addressed in my changes.