• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Blocker Blocker
    • promoted-builds-plugin
    • promoted-builds-plugin 2.28
      Jenkins ver. 2.32.1

      I have a promotion with downstream job and manual conditions:

      						conditions {
      							manual 'acme'
                                                              downstream(false, 'acme-Release-DSL')
      						}

      It has been working correctly for some time.
      Today after giving the manual approval the promotion failed to start.
      The page showed

      This promotion has not happened.
      Met Qualification

      Pressing re-execute promotion opens URL JobName/177/PromotionName/build with a 404 status.

      There are no relevant entries in Jenkins log.
      Job folder on Jenkins master looks OK, the PromotionName folder with logs etc. is there.

      I was only able to execute the promotion by using "Force Promotion". When it executed it got the number immediately following last promotion – it's not a case of promotion being temporarily invisible as in JENKINS-39648

          [JENKINS-41325] Promotions dissapear without a trace

          Oleg Nenashev added a comment -

          So it is about the JobDSL integration. I suppose I need to create an EPIC for it since the stuff is definitely locked on https://github.com/jenkinsci/promoted-builds-plugin/pull/96

          Oleg Nenashev added a comment - So it is about the JobDSL integration. I suppose I need to create an EPIC for it since the stuff is definitely locked on https://github.com/jenkinsci/promoted-builds-plugin/pull/96

          OK, I was (wrongly) assuming using job-dsl results in the exact same configuration as if I used the web form to create a job manually.

          I see this is not true, depending on how a particular step is implemented – thanks for pointing it out.

          Jakub Bochenski added a comment - OK, I was (wrongly) assuming using job-dsl results in the exact same configuration as if I used the web form to create a job manually. I see this is not true, depending on how a particular step is implemented – thanks for pointing it out.

            Unassigned Unassigned
            jbochenski Jakub Bochenski
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: