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

An option flag in the Jenkins Configuration for "trigger builds even if unstable"

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major Major
    • maven-plugin
    • None

      I see there is no way to trigger automatically the downstream build when a project is unstable.
      Is it possible to have a default configuration flag inside the main Jenkins configuration or at least in the project configuration?
      I need it because we have a Maven multi module project, where each module is compiled separately and we need to work at the same time on projects in different downstream steps.
      Jenkins read correctly the upstream and downstream dependencies but when the build is unstable the trigger is not executed, so we can't see if there are any failed tests in the following steps.

      I know it is possible to manually set the "trigger even if unstable" specifying the project to build, but this is a very manual and error prone process difficult to maintain.
      Is there any solution?

          [JENKINS-12540] An option flag in the Jenkins Configuration for "trigger builds even if unstable"

          Daniel Beck added a comment -

          I know it is possible to manually set the "trigger even if unstable" specifying the project to build, but this is a very manual and error prone process difficult to maintain.

          Could you clarify what kind of trigger this issue is about, if not the manual post-build step 'Build other projects'?

          Daniel Beck added a comment - I know it is possible to manually set the "trigger even if unstable" specifying the project to build, but this is a very manual and error prone process difficult to maintain. Could you clarify what kind of trigger this issue is about, if not the manual post-build step 'Build other projects'?

          Hi Daniel, we have a multi module maven project that at the moment build
          all the code in one go using only the configured Maven modules from a
          parent pom file.
          Long ago I tried to build each module separately with Jenkins, knowing that
          it reads and follows the Maven dependency tree.

          It works well for a normal, non testing build, but when running unit tests,
          the build chain breaks if one of the upper dependencies is marked as
          "unstable".
          In this case we had multiple times where the unit tests were not running at
          all in all the sub modules, and went back to run the build all in one
          single project.

          using the post step build is not an option as the maintenance would be so
          much and manual to render the effort counterproductive

          Gian Mario Contessa added a comment - Hi Daniel, we have a multi module maven project that at the moment build all the code in one go using only the configured Maven modules from a parent pom file. Long ago I tried to build each module separately with Jenkins, knowing that it reads and follows the Maven dependency tree. It works well for a normal, non testing build, but when running unit tests, the build chain breaks if one of the upper dependencies is marked as "unstable". In this case we had multiple times where the unit tests were not running at all in all the sub modules, and went back to run the build all in one single project. using the post step build is not an option as the maintenance would be so much and manual to render the effort counterproductive

          Daniel Beck added a comment -

          OK, now I understand the report. Thanks for the response!

          Reassigning issue to the Maven plugin.

          Daniel Beck added a comment - OK, now I understand the report. Thanks for the response! Reassigning issue to the Maven plugin.

            Unassigned Unassigned
            conte Gian Mario Contessa
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: