![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
current |
|
Assignee:
|
Unassigned |
|
Components:
|
core |
|
Created:
|
19/Nov/13 3:44 AM
|
|
Description:
|
I've noticed for a long time that deleting a job in Jenkins is flakey - it often deletes MOST of the job, but leaves a config file around, causing that job to spring back into existence with no history/builds later on.
Is there perhaps some sort of concurrency issue where the delete is trying to run at the same time as another thread is rewriting the job config because of changes?
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Nathan Neulinger
|
|
|
|
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.
