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

Promotion fails if the Parameterized trigger returns unstable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • promoted-builds-plugin
    • None
    • Jenkins ver. 1.642.2 with plugin 2.25, running on Windows 2008 server with JDK 8 Update 74

      We upgraded to Jenkins ver. 1.642.2 with plugin 2.25 yesterday. Now promotions that are unstable show red, instead of the regular color the icon should be.

      The workaround is to "never" mark the promotion on unstable promotions.

      The issue is high because we have 1000s of builds, and we are being flooded with calls right.

          [JENKINS-33393] Promotion fails if the Parameterized trigger returns unstable

          jurgezero added a comment -

          Changed bug to critical, because its not just changing the icon, its actually failing the promotion when the last "Trigger/call builds on other project" with "Block until the triggered project finish their builds" enabled is unstable in the promotion. I noticed that if you have more than one "Trigger/call builds on other project", and the first one is Unstable, but the last one is Stable, it works just fine. Only if the last one is unstable it also fails the promotion.

          Rolling back our environment will re-introduce JENKINS-31406 JENKINS-31320 for us. Getting a lot of support calls, and we cannot edit all the jobs to do the workaround. A quick fix would be greatly appreciated. Thank you.

          jurgezero added a comment - Changed bug to critical, because its not just changing the icon, its actually failing the promotion when the last "Trigger/call builds on other project" with "Block until the triggered project finish their builds" enabled is unstable in the promotion. I noticed that if you have more than one "Trigger/call builds on other project", and the first one is Unstable, but the last one is Stable, it works just fine. Only if the last one is unstable it also fails the promotion. Rolling back our environment will re-introduce JENKINS-31406 JENKINS-31320 for us. Getting a lot of support calls, and we cannot edit all the jobs to do the workaround. A quick fix would be greatly appreciated. Thank you.

          Oleg Nenashev added a comment -

          Have you updated both Jenkins core and plugins?
          If yes, which versions have you used before?

          Oleg Nenashev added a comment - Have you updated both Jenkins core and plugins? If yes, which versions have you used before?

          Oleg Nenashev added a comment -

          Have you also updated the Parameterized trigger plugin?

          Oleg Nenashev added a comment - Have you also updated the Parameterized trigger plugin?

          jurgezero added a comment -

          Currently we have core 1.642.2 with promoted-builds plugin 2.25. Versoin 2.29 of parameterized-trigger is installed.

          Before the upgrade we had core 1.609.1 with promoted-builds 2.2.2

          Thank you.

          jurgezero added a comment - Currently we have core 1.642.2 with promoted-builds plugin 2.25. Versoin 2.29 of parameterized-trigger is installed. Before the upgrade we had core 1.609.1 with promoted-builds 2.2.2 Thank you.

          Oleg Nenashev added a comment -

          Sorry, over last months I had no time to work on the plugin, because I had to focus on the Jenkins core and other projects. I also have not been using this plugin on my own since 2016. So I have decided to unassign the issues so that there is no expectation that I work on them anytime soon.

          Currently the plugin is being transfered to another maintainer. Hopefully he will have some time to finish triaging of the issues and maybe to deliver some fixes. But, as in any community-driven project, everybody is welcome to propose pull requests and to contribute to the plugin's state.

          Oleg Nenashev added a comment - Sorry, over last months I had no time to work on the plugin, because I had to focus on the Jenkins core and other projects. I also have not been using this plugin on my own since 2016. So I have decided to unassign the issues so that there is no expectation that I work on them anytime soon. Currently the plugin is being transfered to another maintainer. Hopefully he will have some time to finish triaging of the issues and maybe to deliver some fixes. But, as in any community-driven project, everybody is welcome to propose pull requests and to contribute to the plugin's state.

            Unassigned Unassigned
            jurgens00 jurgezero
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: