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

auto build of downstream projects doesn't workfor m2 jobs in unstable state, when using surefire flag testFailureIgnore

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major Major
    • maven-plugin
    • None
    • Platform: Sun, OS: Solaris

      I have a job which use the maven2 native support. This one has some downstream
      projects.
      If the upstream projects has an unstable state, the downstream projects are not
      build even if upstream projects have the surefire flag testFailureIgnore set to
      true.

          [JENKINS-3122] auto build of downstream projects doesn't workfor m2 jobs in unstable state, when using surefire flag testFailureIgnore

          Andrew Bayer added a comment -

          Duplicate of 2598.

              • This issue has been marked as a duplicate of 2598 ***

          Andrew Bayer added a comment - Duplicate of 2598. This issue has been marked as a duplicate of 2598 ***

          erimag added a comment -

          I disagree that this is a duplicate of 2598. That issue deals with the "trigger even if the build is unstable" explicit checkbox set in Hudson.

          My interpretation of this issue is that a Maven2 build should automatically implement this behaviour (i.e. trigger downstream builds) if the build is unstable AND the pom has the flag "testFailureIgnore" set to true as below:

          <plugin>
          	<groupId>org.apache.maven.plugins</groupId>
          	<artifactId>maven-surefire-plugin</artifactId>
          	<configuration>
          		<testFailureIgnore>true</testFailureIgnore>
          	</configuration>
          </plugin>
          

          This should happen regardless of if the "trigger even if the build is unstable" is set explicitely on the Hudson job. I agree that this should be seen as an enhancement, but I think it should be re-opened as an independent issue.

          erimag added a comment - I disagree that this is a duplicate of 2598. That issue deals with the "trigger even if the build is unstable" explicit checkbox set in Hudson. My interpretation of this issue is that a Maven2 build should automatically implement this behaviour (i.e. trigger downstream builds) if the build is unstable AND the pom has the flag "testFailureIgnore" set to true as below: <plugin> <groupId> org.apache.maven.plugins </groupId> <artifactId> maven-surefire-plugin </artifactId> <configuration> <testFailureIgnore> true </testFailureIgnore> </configuration> </plugin> This should happen regardless of if the "trigger even if the build is unstable" is set explicitely on the Hudson job. I agree that this should be seen as an enhancement, but I think it should be re-opened as an independent issue.

          evernat added a comment -

          The suggested improvement is related to JENKINS-2598 ("trigger even if the build is unstable" checkbox) but it is not a duplicate.

          evernat added a comment - The suggested improvement is related to JENKINS-2598 ("trigger even if the build is unstable" checkbox) but it is not a duplicate.

          evernat added a comment -

          Hi Olivier,
          Do you still think that this is a good to have improvement?
          Thanks,Emeric

          evernat added a comment - Hi Olivier, Do you still think that this is a good to have improvement? Thanks,Emeric

          Olivier Lamy added a comment -

          Perso I don't need it anymore.
          We can leave it as Open in a backlogs ?

          Olivier Lamy added a comment - Perso I don't need it anymore. We can leave it as Open in a backlogs ?

          evernat added a comment -

          I am not sure that the testFailureIgnore surefire flag in pom.xml should be used to change in Jenkins the behavior of the triggering of the downstream projects if "unstable", but still I am ok to keep it open "just in case".

          evernat added a comment - I am not sure that the testFailureIgnore surefire flag in pom.xml should be used to change in Jenkins the behavior of the triggering of the downstream projects if "unstable", but still I am ok to keep it open "just in case".

          Peter Murray added a comment -

          Correct me if I'm wrong, but currently there is no way - even explicitly - to indicate that Jenkins should build downstream dependencies that are introduced from the "build when SNAPSHOTS are built" maven configuration option?

          I love that Jenkins can discover these inter-project dependencies, but would like to be able to kick off downstream builds even when tests are failing. Personally I don't care if it triggers on the "testFailureIgnore" flag or if it is a project or global configuration option.

          Any thoughts? Should I look at it and submit a patch?

          Peter Murray added a comment - Correct me if I'm wrong, but currently there is no way - even explicitly - to indicate that Jenkins should build downstream dependencies that are introduced from the "build when SNAPSHOTS are built" maven configuration option? I love that Jenkins can discover these inter-project dependencies, but would like to be able to kick off downstream builds even when tests are failing. Personally I don't care if it triggers on the "testFailureIgnore" flag or if it is a project or global configuration option. Any thoughts? Should I look at it and submit a patch?

          Adam H added a comment -

          @peter:
          Yes, I would appreciate that a lot. I'm using the warnings plugin and want my builds to turn yellow on warnings, while still kicking off downstream jobs.

          Adam H added a comment - @peter: Yes, I would appreciate that a lot. I'm using the warnings plugin and want my builds to turn yellow on warnings, while still kicking off downstream jobs.

          Justin Wesley added a comment -

          I'm with @Adam H on this one. I want the build to be yellow if I have test failures, but still want downstream jobs to run as well.

          Justin Wesley added a comment - I'm with @Adam H on this one. I want the build to be yellow if I have test failures, but still want downstream jobs to run as well.

          I really could need this feature and am willing to help out here. Any hints for me where to start looking in the sources?

          Thomas Reinhardt added a comment - I really could need this feature and am willing to help out here. Any hints for me where to start looking in the sources?

            Unassigned Unassigned
            olamy Olivier Lamy
            Votes:
            7 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated: