For some reason after updating to the latest jenkins and promoted-builds plugin, the re-execute button is not shown after a build has been promoted.

      This used to be available for all builds and is no longer there.

        1. promoted-builds-2.18-20140807.061532-2.hpi
          226 kB
        2. JenkinsBugTest.zip
          148 kB
        3. bug.tgz
          3 kB
        4. bug.tgz
          3 kB

          [JENKINS-20492] Re-Execute promotion button is gone

          gary ogden created issue -

          I am experiencing this same bug. If I use the Force Promotion button to promote a build the re-execute promotion button never appears and I have to kick off another build to redo a promotion. This is a pretty serious problem for me.

          Erik Ylvisaker added a comment - I am experiencing this same bug. If I use the Force Promotion button to promote a build the re-execute promotion button never appears and I have to kick off another build to redo a promotion. This is a pretty serious problem for me.

          Damien Nozay added a comment -

          IMHO, this is coming from:
          https://github.com/jenkinsci/promoted-builds-plugin/commit/9395ed5d781ac93fcd6baf629e99a2f0048a05aa

          there was a change to src/main/resources/hudson/plugins/promoted_builds/PromotedBuildAction/index.jelly
          which introduced a condition

          <j:if test="${!p.isManuallyApproved()}">

          Damien Nozay added a comment - IMHO, this is coming from: https://github.com/jenkinsci/promoted-builds-plugin/commit/9395ed5d781ac93fcd6baf629e99a2f0048a05aa there was a change to src/main/resources/hudson/plugins/promoted_builds/PromotedBuildAction/index.jelly which introduced a condition <j: if test= "${!p.isManuallyApproved()}" >

          Clecio Varjao added a comment -

          The manually approved "re-execute" button just moved into the Badge:
          https://github.com/jenkinsci/promoted-builds-plugin/blob/9395ed5d781ac93fcd6baf629e99a2f0048a05aa/src/main/resources/hudson/plugins/promoted_builds/conditions/ManualCondition/Badge/index.jelly#L12

          The previous re-execute should was preserved for the non-manual promotion (as you pointed out).

          Can you provide with more details of the job? what conditions do you have?

          Clecio Varjao added a comment - The manually approved "re-execute" button just moved into the Badge: https://github.com/jenkinsci/promoted-builds-plugin/blob/9395ed5d781ac93fcd6baf629e99a2f0048a05aa/src/main/resources/hudson/plugins/promoted_builds/conditions/ManualCondition/Badge/index.jelly#L12 The previous re-execute should was preserved for the non-manual promotion (as you pointed out). Can you provide with more details of the job? what conditions do you have?

          Jeff Wehrwein added a comment -

          I also have this problem. The re-execute promotion option seems to disappear only when I've checked the "only when manually approved" checkbox. If I uncheck that box, the re-execute button reappears.

          The manually approved "re-execute" button just moved into the Badge:

          Forgive my ignorance, but I don't understand this explanation - where exactly do I find the re-execute button then?

          The previous re-execute should was preserved for the non-manual promotion (as you pointed out).

          Are you saying that manual promotions are not allowed to be re-executed? If so, why not? Put another way, Damien Nozay pointed out an if condition for manual promotions - why does that condition exist?

          Jeff Wehrwein added a comment - I also have this problem. The re-execute promotion option seems to disappear only when I've checked the "only when manually approved" checkbox. If I uncheck that box, the re-execute button reappears. The manually approved "re-execute" button just moved into the Badge: Forgive my ignorance, but I don't understand this explanation - where exactly do I find the re-execute button then? The previous re-execute should was preserved for the non-manual promotion (as you pointed out). Are you saying that manual promotions are not allowed to be re-executed? If so, why not? Put another way, Damien Nozay pointed out an if condition for manual promotions - why does that condition exist?

          Scott Roberts added a comment -

          I have the same question as above, what does "The manually approved "re-execute" button just moved into the Badge" mean. I can't find this ability to re-execute and it's a real problem for our users.

          Scott Roberts added a comment - I have the same question as above, what does "The manually approved "re-execute" button just moved into the Badge" mean. I can't find this ability to re-execute and it's a real problem for our users.

          Sam Xiao added a comment -

          +1 with sdr984

          What does it even mean by "Badge"??

          Sam Xiao added a comment - +1 with sdr984 What does it even mean by "Badge"??

          Vincent Mos added a comment -

          I like to add i also have problems with the Rexecute Button that is not shown. I have a job with 3 different promotion tasks. Two Of them show the reexecute button. One of them isn't. I can not find any difference in the configuration between the 3 that justifies this difference.

          Vincent Mos added a comment - I like to add i also have problems with the Rexecute Button that is not shown. I have a job with 3 different promotion tasks. Two Of them show the reexecute button. One of them isn't. I can not find any difference in the configuration between the 3 that justifies this difference.

          Trey Duskin added a comment -

          I am also surprised to see that there is no 're-execute promotion' button. We use the promotion function to deploy software to infrastructure. The 're-execute promotion' on an old build would be a great way to roll back software.

          Trey Duskin added a comment - I am also surprised to see that there is no 're-execute promotion' button. We use the promotion function to deploy software to infrastructure. The 're-execute promotion' on an old build would be a great way to roll back software.

          Scott Roberts added a comment -

          The only work around I found for this issue is to make sure you do an 'Approve' promotion first instead of 'Force Promotion'. If you do a force promotion first, there is no re-execute.

          Scott Roberts added a comment - The only work around I found for this issue is to make sure you do an 'Approve' promotion first instead of 'Force Promotion'. If you do a force promotion first, there is no re-execute.

            cvarjao Clecio Varjao
            oggie gary ogden
            Votes:
            7 Vote for this issue
            Watchers:
            13 Start watching this issue

              Created:
              Updated: