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

"trigger even if the build is unstable" is not honored in Maven builds

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Major
    • Resolution: Duplicate
    • maven-plugin
    • None
    • Platform: PC, OS: All

    Description

      I have a multi modules maven project
      I launch a hudson job for this project with multiple maven2 goals:

      test pmd:pmd cobertura:cobertura

      The post action (build another job) doesn't work even if i checked
      the box "trigger even the build is unstable"
      My project seems unstable (yellow)
      but the job after is never launched

      Attachments

        Issue Links

          Activity

            abayer Andrew Bayer added a comment -

            Patch looks good - I'll put it through some testing tomorrow and (assuming no
            problems) commit it then, in which case the fix should be live in 1.318.

            abayer Andrew Bayer added a comment - Patch looks good - I'll put it through some testing tomorrow and (assuming no problems) commit it then, in which case the fix should be live in 1.318.
            abayer Andrew Bayer added a comment -

            Ok, on further investigation, this is more confusing than I thought. =) The
            problem here is that the m2 projects' "build when SNAPSHOT dependency builds"
            option feeds into the same mechanics as the post-build trigger (and, for that
            matter, the "build modules in parallel" option relies on the same mechanics as
            well). I'm not sure if we really want the post-build trigger configuration to be
            doing anything to the m2 project-specific dependency build logic, and there's no
            clear way to distinguish between "this project is an m2 project-type dependency"
            and "this project is a build trigger-type dependency". Not to mention that the
            same project could show up in both categories.

            Let me think on this some.

            abayer Andrew Bayer added a comment - Ok, on further investigation, this is more confusing than I thought. =) The problem here is that the m2 projects' "build when SNAPSHOT dependency builds" option feeds into the same mechanics as the post-build trigger (and, for that matter, the "build modules in parallel" option relies on the same mechanics as well). I'm not sure if we really want the post-build trigger configuration to be doing anything to the m2 project-specific dependency build logic, and there's no clear way to distinguish between "this project is an m2 project-type dependency" and "this project is a build trigger-type dependency". Not to mention that the same project could show up in both categories. Let me think on this some.
            abayer Andrew Bayer added a comment -
                • Issue 3884 has been marked as a duplicate of this issue. ***
            abayer Andrew Bayer added a comment - Issue 3884 has been marked as a duplicate of this issue. ***
            abayer Andrew Bayer added a comment -
                • Issue 3122 has been marked as a duplicate of this issue. ***
            abayer Andrew Bayer added a comment - Issue 3122 has been marked as a duplicate of this issue. ***
            evernat evernat added a comment -

            Duplicates JENKINS-4739, which is already fixed.

            evernat evernat added a comment - Duplicates JENKINS-4739 , which is already fixed.

            People

              abayer Andrew Bayer
              ptvngagmail ptvngagmail
              Votes:
              7 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: