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

Renamin promotion process doesn't remove the original promotion process

    XMLWordPrintable

Details

    Description

      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

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-27716 Copying A Job With Promotions and Renaming New Promotion Causes Phantom Promotions

          • Major - Major loss of function.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-10423 Builds get double promotions after promotion has been renamed

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-12799 When project configuration is changed, Promoted Builds Plugin continues to use "old" configuration data

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Activity

            Ascending order - Click to sort in descending order
            View 5 older comments
            mpeters 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.

            mpeters 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.
            mpeters 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.

            mpeters 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.
            gradalajage 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.

            gradalajage 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.
            aheritier 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

            aheritier 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
            mpeters 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.

            mpeters 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.

            People

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

              Dates

                Created:
                Updated:
                Resolved: