![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Frédéric Camblor
|
|
Components:
|
scm-sync-configuration-plugin |
|
Created:
|
26/Nov/14 2:29 AM
|
|
Description:
|
Renaming a job causes a commit to be added to the scm-sync plug-in's internal commit queue (see ScmSyncConfigurationBusiness.java) that fails due to the issue documented in JENKINS-15128 - Renaming job doesn't work with Git. Thereafter, even if one cleans up the checkoutConfiguration directory and manually syncs everything up, it become necessary to restart Jenkins because the failed commit poisons the queue. The remaining issue with 15128 (not calling git rm with the recursive flag) means the commit can never succeed. All subsequent configuration changes get stuck behind it.
There needs to be a way to reset the queue queue w/o restarting Jenkins.
|
|
Environment:
|
Jenkins v 1.552 scm-sync v 0.0.8
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
Kenneth Baltrinic
|
|
|
|
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.
