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

maven project fails build when log claims with success.

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • maven-plugin
    • None
    • ubuntu 10.04
      jenkins 1.573
      maven 3.2.1
      java 7u25
      jenkins maven plugin 2.4
      sonar plugin 2.1

      When building a project as a maven plugin, the weather marker and sonar plugin call the build failed, but at the end of the log it reports success.

      Also, when I run this build with the exact same setup and plugins, but as a freestyle project instead of a maven project, it succeeds.

        1. build-reports.txt
          20 kB
        2. build-results-2.txt
          3 kB
        3. freestyle-bc.log
          775 kB
        4. freestyle-config.xml
          5 kB
        5. jenkins_build-log
          488 kB
        6. maven-config.xml
          488 kB
        7. problem-pom.xml
          30 kB

          [JENKINS-24228] maven project fails build when log claims with success.

          Sean Abbott added a comment -

          The sonar folks sent me the line number where they fetch the build result, but it's on my other computer. I'll post it in an hour when I'm out of this meeting.

          Sean Abbott added a comment - The sonar folks sent me the line number where they fetch the build result, but it's on my other computer. I'll post it in an hour when I'm out of this meeting.

          Sean Abbott added a comment - https://github.com/SonarSource/jenkins-sonar-plugin/blob/master/src/main/java/hudson/plugins/sonar/model/TriggersConfig.java#L90

          Daniel Beck added a comment -

          Yeah that was pretty obvious. Hence the request to get the API while it's building to see what that value is then.

          Daniel Beck added a comment - Yeah that was pretty obvious. Hence the request to get the API while it's building to see what that value is then.

          Sean Abbott added a comment -

          A number of reports grabbed during the build. number 6 was grabbed immediately after it finished running maven.

          Sean Abbott added a comment - A number of reports grabbed during the build. number 6 was grabbed immediately after it finished running maven.

          Sean Abbott added a comment -

          Was there a different api call besides just grabbing the json I was supposed to do? I don't really see any new info in that. :-/

          Pastebin of the "most likely relevant" reading: http://pastebin.com/H9dLxh9A

          Sean Abbott added a comment - Was there a different api call besides just grabbing the json I was supposed to do? I don't really see any new info in that. :-/ Pastebin of the "most likely relevant" reading: http://pastebin.com/H9dLxh9A

          Daniel Beck added a comment -

          I'm sorry, that was the wrong URL – please repeat the API access for /job/jobname/buildnumber/api/json with 'buildnumber' the number of the currently running build at around the time it skips Sonar.

          Daniel Beck added a comment - I'm sorry, that was the wrong URL – please repeat the API access for /job/jobname/buildnumber/api/json with 'buildnumber' the number of the currently running build at around the time it skips Sonar.

          Sean Abbott added a comment -

          Ok, the second one here was grabbed right after maven finished and reported success, while the CLM can was running.

          Sean Abbott added a comment - Ok, the second one here was grabbed right after maven finished and reported success, while the CLM can was running.

          Sean Abbott added a comment -

          I would delete the extraneous build-reports.txt file, but it won't let me.

          Sean Abbott added a comment - I would delete the extraneous build-reports.txt file, but it won't let me.

          Daniel Beck added a comment -

          I'm out of good ideas.

          It seems weird that no artifacts are recorded for the build, but that may well be regular behavior, I just don't know.

          Daniel Beck added a comment - I'm out of good ideas. It seems weird that no artifacts are recorded for the build, but that may well be regular behavior, I just don't know.

          Sean Abbott added a comment -

          Well, and it's also weird because even though it claims failure, all the tests pass and the artifacts are successfully uploaded to the nexus artifact repository.

          Sean Abbott added a comment - Well, and it's also weird because even though it claims failure, all the tests pass and the artifacts are successfully uploaded to the nexus artifact repository.

            Unassigned Unassigned
            seanabbott Sean Abbott
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: