Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-25786

Renaming Job Causes a poisoned commitQueue

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Critical Critical
    • None
    • Jenkins v 1.552 scm-sync v 0.0.8

      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.

            Unassigned Unassigned
            kbaltrinic Kenneth Baltrinic
            Votes:
            9 Vote for this issue
            Watchers:
            20 Start watching this issue

              Created:
              Updated:
              Resolved: