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

Renamin promotion process doesn't remove the original promotion process

      Create a promotion process that is dependent on a downstream build and save
      Rename that promotion process and save again
      Kick off downstream build and 2 promotion processes will be kicked off, the old name and the new name

          [JENKINS-8783] Renamin promotion process doesn't remove the original promotion process

          Is there a work-around for this?

          John Muczynski added a comment - Is there a work-around for this?

          Okay, so to delete the undeleted stuff, it looks like you do this:

          go into the Jenkins directory on the master
          go into the subdirectory for the job
          see the subdirectory for promotions?
          Go in there and delete whatever offends you.

          Um, maybe make a backup of everything before you start, eh?

          John Muczynski added a comment - Okay, so to delete the undeleted stuff, it looks like you do this: go into the Jenkins directory on the master go into the subdirectory for the job see the subdirectory for promotions? Go in there and delete whatever offends you. Um, maybe make a backup of everything before you start, eh?

          Markus added a comment -

          I'm seeing the same thing. Jenkins ver. 1.439. Jenkins promoted builds plugin 2.4

          Markus added a comment - I'm seeing the same thing. Jenkins ver. 1.439. Jenkins promoted builds plugin 2.4

          This doesn't reproduce anymore with Jenkins v1.488 and promoted-builds-plugin v2.8. It's probably a duplicate of JENKINS-12799 which has been fixed in v2.8?

          Tuukka Mustonen added a comment - This doesn't reproduce anymore with Jenkins v1.488 and promoted-builds-plugin v2.8. It's probably a duplicate of JENKINS-12799 which has been fixed in v2.8?

          Owen Mehegan added a comment -

          Definitely fixed at least in version 2.10 of the plugin.

          Owen Mehegan added a comment - Definitely fixed at least in version 2.10 of the plugin.

          I'm seeing this happen again on v2.22 of this plugin.

          We renamed a promotion process and it resulted in double stars. We changed the name back and added a 2nd identical promotion process with the new name and deleted the old one. Still results in double stars.

          Michael Peters added a comment - I'm seeing this happen again on v2.22 of this plugin. We renamed a promotion process and it resulted in double stars. We changed the name back and added a 2nd identical promotion process with the new name and deleted the old one. Still results in double stars.

          I should note, that this is happening to a job inside of a new folder. I don't know if that would make a difference or not.

          Michael Peters added a comment - I should note, that this is happening to a job inside of a new folder. I don't know if that would make a difference or not.

          Kyle Estes added a comment -

          I saw this in v2.19. I thought updating to latest might fix it, but it continues to happen in v2.23.1. Like mpeters this is happening for a job in a folder.

          Kyle Estes added a comment - I saw this in v2.19. I thought updating to latest might fix it, but it continues to happen in v2.23.1. Like mpeters this is happening for a job in a folder.

          This is not related to the usage of folders (the same problem exists without it).

          Workaround:

          • Open you job configuration
          • Add new promotion with the previous name before the renaming. They can be empty. Myself I just checked "Promote immediately once the build is complete"
          • Save your configuration
          • Open you job configuration a second time
          • Remove the promotion with the old name
          • Save your configuration

          Your job should now work correctly without breaking old promotions and the object model.

          The issue will be fixed by JENKINS-27716 in promotion plugin > 2.23.1 if you are running on Jenkins >= 1.585

          Arnaud Héritier added a comment - This is not related to the usage of folders (the same problem exists without it). Workaround: Open you job configuration Add new promotion with the previous name before the renaming. They can be empty. Myself I just checked "Promote immediately once the build is complete" Save your configuration Open you job configuration a second time Remove the promotion with the old name Save your configuration Your job should now work correctly without breaking old promotions and the object model. The issue will be fixed by JENKINS-27716 in promotion plugin > 2.23.1 if you are running on Jenkins >= 1.585

          I actually tried this work around multiple times with v2.22 and it did not fix it. Hopefully 2.23.1 fixes this.

          Michael Peters added a comment - I actually tried this work around multiple times with v2.22 and it did not fix it. Hopefully 2.23.1 fixes this.

            petehayes Peter Hayes
            petehayes Peter Hayes
            Votes:
            8 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: