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

module-pom failures do not trigger mails (was: m2extra-steps stops build failure mails)

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • maven-plugin
    • None
    • Platform: All, OS: All

      Hudson 1.313, m2extrasteps 1.1

      To reproduce:
      1. create new m2 build job
      2. check email-notification (with Send e-mail for every unstable build and Send
      separate e-mails to individuals who broke the build)
      3. add post build step with unix shell command (Run regardless of build result)

      If the main m2 build fails no failure mails are sent.

          [JENKINS-3955] module-pom failures do not trigger mails (was: m2extra-steps stops build failure mails)

          Andrew Bayer added a comment -

          Hi - I'm not able to duplicate this so far. I don't have the email to
          individuals who broke the build enabled (since my test environment isn't using
          source from source control, so that I know it'll break), but I am getting the
          global emails for build failure. Can you confirm that emails are being sent
          properly with the m2 extra steps disabled?

          Andrew Bayer added a comment - Hi - I'm not able to duplicate this so far. I don't have the email to individuals who broke the build enabled (since my test environment isn't using source from source control, so that I know it'll break), but I am getting the global emails for build failure. Can you confirm that emails are being sent properly with the m2 extra steps disabled?

          I did some additional research, it seems to be a general maven2-job bug (sorry
          for assigning it to m2extrasteps).
          If a sub-pom fails resolving an artifact no emails are sent.
          Tested with 2.0.9 and 2.1.0
          If there is a simply compile error mails are getting sent.

          Maybe someone can retry to reproduce using these steps:
          1. create new m2 build job and use the project structure in the attached zip
          2. check email-notification and add an recipent (and check "Send e-mail for
          every unstable build")

          Result: no mail, output:

          [INFO] ------------------------------------------------------------------------
          [ERROR] BUILD ERROR
          [INFO] ------------------------------------------------------------------------
          [INFO] Failed to resolve artifact.

          Missing:
          ----------
          1) delta:delta:jar:error-in-version-number

          Try downloading the file manually from the project website.

          Then, install it using the command:
          mvn install:install-file -DgroupId=delta -DartifactId=delta
          -Dversion=error-in-version-number -Dpackaging=jar -Dfile=/path/to/file

          Alternatively, if you host your own repository you can deploy the file there:
          mvn deploy:deploy-file -DgroupId=delta -DartifactId=delta
          -Dversion=error-in-version-number -Dpackaging=jar -Dfile=/path/to/file
          -Durl=[url] -DrepositoryId=[id]

          Path to dependency:
          1) pos:iac:jar:1.0.0-SNAPSHOT
          2) delta:delta:jar:error-in-version-number

          ----------
          1 required artifact is missing.

          for artifact:
          pos:iac:jar:1.0.0-SNAPSHOT

          from the specified remote repositories:
          artifactory (http://maven.example.at/artifacts/repo)

          [INFO] ------------------------------------------------------------------------
          [INFO] For more information, run Maven with the -e switch
          [INFO] ------------------------------------------------------------------------
          [INFO] Total time: 4 seconds
          [INFO] Finished at: Wed Jul 01 17:07:46 CEST 2009
          [INFO] Final Memory: 11M/167M
          [INFO] ------------------------------------------------------------------------
          channel stopped
          Finished: FAILURE

          Florian Rosenauer added a comment - I did some additional research, it seems to be a general maven2-job bug (sorry for assigning it to m2extrasteps). If a sub-pom fails resolving an artifact no emails are sent. Tested with 2.0.9 and 2.1.0 If there is a simply compile error mails are getting sent. Maybe someone can retry to reproduce using these steps: 1. create new m2 build job and use the project structure in the attached zip 2. check email-notification and add an recipent (and check "Send e-mail for every unstable build") Result: no mail, output: [INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Failed to resolve artifact. Missing: ---------- 1) delta:delta:jar:error-in-version-number Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=delta -DartifactId=delta -Dversion=error-in-version-number -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=delta -DartifactId=delta -Dversion=error-in-version-number -Dpackaging=jar -Dfile=/path/to/file -Durl= [url] -DrepositoryId= [id] Path to dependency: 1) pos:iac:jar:1.0.0-SNAPSHOT 2) delta:delta:jar:error-in-version-number ---------- 1 required artifact is missing. for artifact: pos:iac:jar:1.0.0-SNAPSHOT from the specified remote repositories: artifactory ( http://maven.example.at/artifacts/repo ) [INFO] ------------------------------------------------------------------------ [INFO] For more information, run Maven with the -e switch [INFO] ------------------------------------------------------------------------ [INFO] Total time: 4 seconds [INFO] Finished at: Wed Jul 01 17:07:46 CEST 2009 [INFO] Final Memory: 11M/167M [INFO] ------------------------------------------------------------------------ channel stopped Finished: FAILURE

          Created an attachment (id=763)
          two dependent poms with a wrong dependency to fail the build

          Florian Rosenauer added a comment - Created an attachment (id=763) two dependent poms with a wrong dependency to fail the build

          has been resolved with Bug #1066

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

          Florian Rosenauer added a comment - has been resolved with Bug #1066 This issue has been marked as a duplicate of 1066 ***

          all my Problems from
          http://www.nabble.com/should-every-failed-build-trigger-an-e-mail--to25041790.html
          have been solved, thank you!

          • if the maven job type fails because someone changed the JDK to 1.4.2 or lower
          • if maven job type fails because it cannot resolve a dependency
          • if a maven job type does not find a pom.xml because someone accidentally
            deleted it from the repository
          • if a pom.xml is invalid and cannot be parsed

          Florian Rosenauer added a comment - all my Problems from http://www.nabble.com/should-every-failed-build-trigger-an-e-mail--to25041790.html have been solved, thank you! if the maven job type fails because someone changed the JDK to 1.4.2 or lower if maven job type fails because it cannot resolve a dependency if a maven job type does not find a pom.xml because someone accidentally deleted it from the repository if a pom.xml is invalid and cannot be parsed

            abayer Andrew Bayer
            skybird Florian Rosenauer
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: