• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • maven-plugin
    • Windows 7, Linux
    • 1.532.1

      Since Jenkins version 1.526 my Console Logs do not log any Maven errors. Version 1.525 was still ok.

      To reproduce this I tried deploying artifacts to a bogus repository, normally I would get something like this:
      message : Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin...

      But there is nothing now. Using Maven 3.0 or 3.1 makes no difference as well as calling Maven with -e or -X.

      Jenkins and Maven plugin are at the same version (tried it with 1.526 and 1.528) only version 1.525 and lower gave me error messages in the log.

          [JENKINS-19352] Maven logs no errors

          The bug appeared when I installed your fix from dropbox that you linked earlier in this thread. So I'm quite sure it has to do with what ever you changed in that fix. But is JENKINS-1201 included in Maven-plugin 2.0-beta1?

          But of course I can create a new JIRA issue for this, it is always nice to have the bugs down on paper.

          Andreas Magnusson added a comment - The bug appeared when I installed your fix from dropbox that you linked earlier in this thread. So I'm quite sure it has to do with what ever you changed in that fix. But is JENKINS-1201 included in Maven-plugin 2.0-beta1? But of course I can create a new JIRA issue for this, it is always nice to have the bugs down on paper.

          I created a JIRA issue now, JENKINS-20209. Didn't now who to assign it to though.

          Andreas Magnusson added a comment - I created a JIRA issue now, JENKINS-20209 . Didn't now who to assign it to though.

          cforce added a comment -

          Same Here. Discusting.

          cforce added a comment - Same Here. Discusting.

          @cforce:
          What are you referring to?

          Torsten Mingers added a comment - @cforce: What are you referring to?

          I've just built and installed 2.1-SNAPSHOT (last commit id: 3380985e5584d40f6988f3d7cf6fcc587f4246bb) and the errors are now correctly reported and mail are sent to all recipients with no problem.
          Thanks for the fix.

          Cédric Lamalle added a comment - I've just built and installed 2.1-SNAPSHOT (last commit id: 3380985e5584d40f6988f3d7cf6fcc587f4246bb) and the errors are now correctly reported and mail are sent to all recipients with no problem. Thanks for the fix.

          Hi everyone,

          we are currently running Jenkins ver. 1.535 and experiencing this issue as well. Now that LTS 1.532.1 has been released on 25th of Nov, I am wondering if this fix has been integrated. The issue JENKINS-19352 is not mentioned in the changelog (http://jenkins-ci.org/changelog-stable).

          Maybe I am missing the information for some reason so I'd be grateful if someone could point out if LTS 1.532.1 includes this fix. Or, if not, if there will be a LTS release in the foreseeable future.

          Thanks for all the efforts

          Henrik Steudel added a comment - Hi everyone, we are currently running Jenkins ver. 1.535 and experiencing this issue as well. Now that LTS 1.532.1 has been released on 25th of Nov, I am wondering if this fix has been integrated. The issue JENKINS-19352 is not mentioned in the changelog ( http://jenkins-ci.org/changelog-stable ). Maybe I am missing the information for some reason so I'd be grateful if someone could point out if LTS 1.532.1 includes this fix. Or, if not, if there will be a LTS release in the foreseeable future. Thanks for all the efforts

          Eric Rizzo added a comment -

          Sorry if the answer is buried in all the comments and metadata (I've read through everything twice), but I can't determine if this fix is in any release of Jenkins other than the LTS 1.532.1 and later. Can anyone confirm precisely which releases I can get that include this fix?

          Eric Rizzo added a comment - Sorry if the answer is buried in all the comments and metadata (I've read through everything twice), but I can't determine if this fix is in any release of Jenkins other than the LTS 1.532.1 and later. Can anyone confirm precisely which releases I can get that include this fix?

          You will need the Maven Project Plugin in at least version 2.0 (latest version is 2.8). This plugin needs Jenkins 1.532+ (1.538+ for latest version).

          Torsten Mingers added a comment - You will need the Maven Project Plugin in at least version 2.0 (latest version is 2.8). This plugin needs Jenkins 1.532+ (1.538+ for latest version).

          This problem has recently re-appeared. This is what I get locally

          ...
          [INFO] ------------------------------------------------------------------------ 
          [INFO] BUILD FAILURE 
          [INFO] ------------------------------------------------------------------------ 
          [INFO] Total time:  02:11 min 
          [INFO] Finished at: 2022-07-04T16:05:44+02:00 
          [INFO] ------------------------------------------------------------------------ 
          [ERROR] Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.9.1-knime:sonar (default-cli) on project knime-hub-execution-shared: "2.4.0-alpha-todo-HUB-2847-remove-manual-health-checks-that-are-automatically-handled-by-quarkus-000001-3ee42ca" is not
          a valid project version. The maximum length is 100 characters. -> [Help 1]
                           
          [ERROR]  
          [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. 
          [ERROR] Re-run Maven using the -X switch to enable full debug logging. 
          [ERROR]  
          [ERROR] For more information about the errors and possible solutions, please read the following articles: 
          [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
          

          But the Jenkins console log only shows

          ...
          15:23:47.259  [INFO] --- sonar-maven-plugin:3.9.1-knime:sonar (default-cli) @ knime-hub-execution-shared ---
          15:23:47.359  [INFO] User cache: /home/****/.sonar/cache
          15:23:48.974  [Pipeline] }
          15:23:49.191  [withMaven] artifactsPublisher - Archive artifact .flattened-pom.xml under com/knime/enterprise/cloud/services/execution/knime-hub-execution-shared/2.4.0-alpha-todo-HUB-2847-remove-manual-health-checks-that-are-automatically-handled-by-quarkus-000001-3ee42ca/knime-hub-execution-shared-2.4.0-alpha-todo-HUB-2847-remove-manual-health-checks-that-are-automatically-handled-by-quarkus-000001-3ee42ca.pom
          

          I'm using Jenkins LTS 2.332.3 with

          • Maven integration plug-in 3.18
          • Pipeline Maven Integration 3.10.0

          Thorsten Meinl added a comment - This problem has recently re-appeared. This is what I get locally ... [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time:  02:11 min [INFO] Finished at: 2022-07-04T16:05:44+02:00 [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.9.1-knime:sonar (default-cli) on project knime-hub-execution-shared: "2.4.0-alpha-todo-HUB-2847-remove-manual-health-checks-that-are-automatically-handled-by-quarkus-000001-3ee42ca" is not a valid project version. The maximum length is 100 characters. -> [Help 1]                  [ERROR]   [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR]   [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException But the Jenkins console log only shows ... 15:23:47.259 [INFO] --- sonar-maven-plugin:3.9.1-knime:sonar (default-cli) @ knime-hub-execution-shared --- 15:23:47.359 [INFO] User cache: /home/****/.sonar/cache 15:23:48.974 [Pipeline] } 15:23:49.191 [withMaven] artifactsPublisher - Archive artifact .flattened-pom.xml under com/knime/enterprise/cloud/services/execution/knime-hub-execution-shared/2.4.0-alpha-todo-HUB-2847-remove-manual-health-checks-that-are-automatically-handled-by-quarkus-000001-3ee42ca/knime-hub-execution-shared-2.4.0-alpha-todo-HUB-2847-remove-manual-health-checks-that-are-automatically-handled-by-quarkus-000001-3ee42ca.pom I'm using Jenkins LTS 2.332.3 with Maven integration plug-in 3.18 Pipeline Maven Integration 3.10.0

          Nikolas Falco added a comment - - edited

          Fill a new bug with updated environment and description please. This bug is very old and closed with success. Rework the same issue does not make sense.

          Nikolas Falco added a comment - - edited Fill a new bug with updated environment and description please. This bug is very old and closed with success. Rework the same issue does not make sense.

            olivergondza Oliver Gondža
            achbine Sabine Achilles
            Votes:
            44 Vote for this issue
            Watchers:
            61 Start watching this issue

              Created:
              Updated:
              Resolved: