|
||||||||
|
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.
@Rob: We run the P4QUICKCLEANWORKSPACE in overnight clean jobs to ensure the workspaces are clean during the day and there are no leftover unused files that make their way into client deliveries. The incremental CI builds that occur throughout the day do not clean the workspace, that would take far too long for each build. Our builds involve over 80Gb per branch consisting of tens of thousands of files and many many build scripts. Ensure these are always perfect and never leave any unused files behind would be impossible. The short answer is that we need to use branches and we need P4QUICKCLEANWORKSPACE to work.
@Morne: Yes, we also don't use the '@' separator as it causes trouble with platform specific tools. You can replace it when you launch Jenkins, e.g.:
%JAVA% -Dhudson.slaves.WorkspaceList=_ -jar jenkins.war
The changes I made do adhere to this convention.