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-results-2.txt
          3 kB
        2. build-reports.txt
          20 kB
        3. problem-pom.xml
          30 kB
        4. maven-config.xml
          488 kB
        5. freestyle-config.xml
          5 kB
        6. freestyle-bc.log
          775 kB
        7. jenkins_build-log
          488 kB

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

          Daniel Beck added a comment -

          Didn't you already report this?

          Daniel Beck added a comment - Didn't you already report this?

          Sean Abbott added a comment -

          I thought I only emailed the list, i didn't think I filed a bug. If I confused myself, I apologize.

          Sean Abbott added a comment - I thought I only emailed the list, i didn't think I filed a bug. If I confused myself, I apologize.

          Sean Abbott added a comment -

          This is the only bug report I've filed.

          Sean Abbott added a comment - This is the only bug report I've filed.

          Sean Abbott added a comment -

          here's the freestyle log for comparison.

          Sean Abbott added a comment - here's the freestyle log for comparison.

          Sean Abbott added a comment -

          Attaching the working freestyle config.

          Sean Abbott added a comment - Attaching the working freestyle config.

          Sean Abbott added a comment -

          And the maven project config.

          Sean Abbott added a comment - And the maven project config.

          Sean Abbott added a comment -

          And the pom for the project in question. We've got 200 maven projects on this server, this is the only one doing this.

          Sean Abbott added a comment - And the pom for the project in question. We've got 200 maven projects on this server, this is the only one doing this.

          Daniel Beck added a comment -

          ... and on IRC probably OK, I asked because this looked so familiar.

          Daniel Beck added a comment - ... and on IRC probably OK, I asked because this looked so familiar.

          Sean Abbott added a comment -

          Yes, also on IRC. I apologize if I'm breaking conventions or being rude. I have reached hair pulling stage, though.

          Sean Abbott added a comment - Yes, also on IRC. I apologize if I'm breaking conventions or being rude. I have reached hair pulling stage, though.

          Daniel Beck added a comment -

          Sonar plugin version?

          Daniel Beck added a comment - Sonar plugin version?

          Daniel Beck added a comment -

          While the Maven job is building, access the job's API at /job/jobname/api/xml or /job/jobname/api/json and look what the result is that the build reports.

          Daniel Beck added a comment - While the Maven job is building, access the job's API at /job/jobname/api/xml or /job/jobname/api/json and look what the result is that the build reports.

          Daniel Beck added a comment -

          Where's the 44 years old claim?

          Daniel Beck added a comment - Where's the 44 years old claim?

          Sean Abbott added a comment -

          Updated the sonar plugin. The 44 year old claim comes and goes, this build may not have had it. I can attach another log that does. I will update the description and title, that's misleading.

          Sean Abbott added a comment - Updated the sonar plugin. The 44 year old claim comes and goes, this build may not have had it. I can attach another log that does. I will update the description and title, that's misleading.

          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: