![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Assignee:
|
Rob Petti
|
|
Components:
|
perforce |
|
Created:
|
08/Aug/14 8:54 PM
|
|
Description:
|
It would be much more efficient to have an option for Jenkins to delete the workspace at the end of the build job. While the Jenkins perforce plugin is really good about creating and managing workspaces, currently it ends up creating lots of clients/workspaces without cleaning any up. Since the perforce server has to track a lot of metadata on each client workspace (records on each of the files that are checked out), it can severely limit the scalability of the Jenkins/perforce plugin using workspace management.
In a production atmosphere with hundreds to thousands of jobs that can run on different nodes, the perforce server can even run out of RAM loading all the client records into memory. This often leads to the perforce admin hunting down members of the devops team.
|
|
Environment:
|
Jenkins 1.554.2, perforce plugin 1.3.27, RHEL 5.5
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Caleb Mayeux
|
|
|
|
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.
