[JENKINS-72516] pipeline-maven: warning of unknown Maven version in plugin version 1368.vfb_8509d7b_869

Type: Bug
Resolution: Unresolved
Priority: Minor
Component/s: pipeline-maven-plugin
Labels:
None
Environment:
Jenkins LTS 2.426.2
pipeline-maven 1368.vfb_8509d7b_869
pipeline-maven-api 1368.vfb_8509d7b_869

Similar Issues:
Powered by SuggestiMate

Show
Released As:
1376.v18876d10ce9c

After updating the pipeline-maven and pipeline-maven-api plugin from version 1362.vee39a_d4b_02b_1 to version 1368.vfb_8509d7b_869, I can now see every time withMaven() is invoked a warning message in the job log:

[withMaven] WARNING: You are running an old version of Maven (UNKNOWN), you should update to at least 3.8.x

But withMaven seems to pickup the correct Maven version despite the warning:

1) I have configured Maven tool "Maven 3.9.6" picking the version 3.9.6.

2) The following pipeline:

pipeline {  
  agent { node { label 'linux' } }
  stages { 
    stage('Maven') {
      steps {
          withMaven(maven: "Maven 3.9.6") {
            sh "mvn -U -B -e -v"
         }
      }
    }
  } 
}

creates the output

[withMaven] WARNING: You are running an old version of Maven (UNKNOWN), you should update to at least 3.8.x
+ mvn -U -B -e -v
Picked up JAVA_TOOL_OPTIONS: -Dmaven.ext.class.path="/srv/jenkins-data/node/workspace/DOT-1949-mvn@tmp/withMavenbbe509b0/pipeline-maven-spy.jar" -Dorg.jenkinsci.plugins.pipeline.maven.reportsFolder="/srv/jenkins-data/node/workspace/DOT-1949-mvn@tmp/withMavenbbe509b0"
Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
Maven home: /srv/jenkins-data/node/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.9.6
Java version: 17.0.9, vendor: Eclipse Adoptium, runtime: /usr/lib/jvm/temurin-17-jdk
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.10.0-1160.105.1.el7.x86_64", arch: "amd64", family: "unix"
Finished: SUCCESS

I reverted both plugins back to the previous version 1362.vee39a_d4b_02b_1 and the warning message is gone.

Does not look like a critical issue, but having the warning now with every invocation of withMaven() is very irritating for the users.

is caused by

JENKINS-72386 withMaven exits with unrecognized option --no-transfer-progress when using maven < 3.6.1

Closed

links to

Pull request 758

Pull request 766

Rainer Montag created issue - 2024-01-08 08:59

Rainer Montag made changes - 2024-01-08 09:48

Description

Original: After updating the pipeline-maven and pipeline-maven-api plugin from version 1362.vee39a_d4b_02b_1 to version 1368.vfb_8509d7b_869, I can now see every time withMaven() is invoked a warning message in the job log:

[withMaven] WARNING: You are running an old version of Maven (UNKNOWN), you should update to at least 3.8.x
But withMaven seems to pickup the correct Maven version despite the warning:

1) I have configured Maven tool "Maven 3.9.6" picking the version 3.9.6.

2) The following pipeline:
pipeline {
    agent \{ node { label 'linux' } }
   stages { stage('Maven') {
           steps {
   withMaven(maven: "Maven 3.9.6") {
       sh "mvn -U -B -e -v"
       }
          }
   }
    }
}
creates the output
[withMaven] WARNING: You are running an old version of Maven (UNKNOWN), you should update to at least 3.8.x
+ mvn -U -B -e -v
Picked up JAVA_TOOL_OPTIONS: -Dmaven.ext.class.path="/srv/jenkins-data/node/workspace/DOT-1949-mvn@tmp/withMavenbbe509b0/pipeline-maven-spy.jar" -Dorg.jenkinsci.plugins.pipeline.maven.reportsFolder="/srv/jenkins-data/node/workspace/DOT-1949-mvn@tmp/withMavenbbe509b0"
Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
Maven home: /srv/jenkins-data/node/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.9.6
Java version: 17.0.9, vendor: Eclipse Adoptium, runtime: /usr/lib/jvm/temurin-17-jdk
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.10.0-1160.105.1.el7.x86_64", arch: "amd64", family: "unix"
Finished: SUCCESS

I reverted both plugins back to the previous version 1362.vee39a_d4b_02b_1 and the warning message is gone.

Does not look like a critical issue, but having the warning now with every invocation of withMaven() is very irritating for the users.

New: After updating the pipeline-maven and pipeline-maven-api plugin from version 1362.vee39a_d4b_02b_1 to version 1368.vfb_8509d7b_869, I can now see every time withMaven() is invoked a warning message in the job log:

{code:java}
[withMaven] WARNING: You are running an old version of Maven (UNKNOWN), you should update to at least 3.8.x
{code}

But withMaven seems to pickup the correct Maven version despite the warning:

1) I have configured Maven tool "Maven 3.9.6" picking the version 3.9.6.

2) The following pipeline:
{code}
pipeline {
  agent { node { label 'linux' } }
stages {
    stage('Maven') {
steps {
withMaven(maven: "Maven 3.9.6") {
    sh "mvn -U -B -e -v"
   }
      }
}
}
}
{code}
creates the output
{code}
[withMaven] WARNING: You are running an old version of Maven (UNKNOWN), you should update to at least 3.8.x
+ mvn -U -B -e -v
Picked up JAVA_TOOL_OPTIONS: -Dmaven.ext.class.path="/srv/jenkins-data/node/workspace/DOT-1949-mvn@tmp/withMavenbbe509b0/pipeline-maven-spy.jar" -Dorg.jenkinsci.plugins.pipeline.maven.reportsFolder="/srv/jenkins-data/node/workspace/DOT-1949-mvn@tmp/withMavenbbe509b0"
Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
Maven home: /srv/jenkins-data/node/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.9.6
Java version: 17.0.9, vendor: Eclipse Adoptium, runtime: /usr/lib/jvm/temurin-17-jdk
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.10.0-1160.105.1.el7.x86_64", arch: "amd64", family: "unix"
Finished: SUCCESS
{code}

I reverted both plugins back to the previous version 1362.vee39a_d4b_02b_1 and the warning message is gone.

Does not look like a critical issue, but having the warning now with every invocation of withMaven() is very irritating for the users.

Rainer Montag made changes - 2024-01-08 09:50

Description

Original: After updating the pipeline-maven and pipeline-maven-api plugin from version 1362.vee39a_d4b_02b_1 to version 1368.vfb_8509d7b_869, I can now see every time withMaven() is invoked a warning message in the job log:

{code:java}
[withMaven] WARNING: You are running an old version of Maven (UNKNOWN), you should update to at least 3.8.x
{code}

But withMaven seems to pickup the correct Maven version despite the warning:

1) I have configured Maven tool "Maven 3.9.6" picking the version 3.9.6.

2) The following pipeline:
{code}
pipeline {
  agent { node { label 'linux' } }
stages {
    stage('Maven') {
steps {
withMaven(maven: "Maven 3.9.6") {
    sh "mvn -U -B -e -v"
   }
      }
}
}
}
{code}
creates the output
{code}
[withMaven] WARNING: You are running an old version of Maven (UNKNOWN), you should update to at least 3.8.x
+ mvn -U -B -e -v
Picked up JAVA_TOOL_OPTIONS: -Dmaven.ext.class.path="/srv/jenkins-data/node/workspace/DOT-1949-mvn@tmp/withMavenbbe509b0/pipeline-maven-spy.jar" -Dorg.jenkinsci.plugins.pipeline.maven.reportsFolder="/srv/jenkins-data/node/workspace/DOT-1949-mvn@tmp/withMavenbbe509b0"
Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
Maven home: /srv/jenkins-data/node/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.9.6
Java version: 17.0.9, vendor: Eclipse Adoptium, runtime: /usr/lib/jvm/temurin-17-jdk
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.10.0-1160.105.1.el7.x86_64", arch: "amd64", family: "unix"
Finished: SUCCESS
{code}

I reverted both plugins back to the previous version 1362.vee39a_d4b_02b_1 and the warning message is gone.

Does not look like a critical issue, but having the warning now with every invocation of withMaven() is very irritating for the users.

New: After updating the pipeline-maven and pipeline-maven-api plugin from version 1362.vee39a_d4b_02b_1 to version 1368.vfb_8509d7b_869, I can now see every time withMaven() is invoked a warning message in the job log:
{code:java}
[withMaven] WARNING: You are running an old version of Maven (UNKNOWN), you should update to at least 3.8.x
{code}
But withMaven seems to pickup the correct Maven version despite the warning:

1) I have configured Maven tool "Maven 3.9.6" picking the version 3.9.6.

2) The following pipeline:
{code:java}
pipeline {
  agent { node { label 'linux' } }
stages {
    stage('Maven') {
steps {
withMaven(maven: "Maven 3.9.6") {
    sh "mvn -U -B -e -v"
   }
      }
}
}
}
{code}
creates the output
{code:java}
[withMaven] WARNING: You are running an old version of Maven (UNKNOWN), you should update to at least 3.8.x
+ mvn -U -B -e -v
Picked up JAVA_TOOL_OPTIONS: -Dmaven.ext.class.path="/srv/jenkins-data/node/workspace/DOT-1949-mvn@tmp/withMavenbbe509b0/pipeline-maven-spy.jar" -Dorg.jenkinsci.plugins.pipeline.maven.reportsFolder="/srv/jenkins-data/node/workspace/DOT-1949-mvn@tmp/withMavenbbe509b0"
Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
Maven home: /srv/jenkins-data/node/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.9.6
Java version: 17.0.9, vendor: Eclipse Adoptium, runtime: /usr/lib/jvm/temurin-17-jdk
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.10.0-1160.105.1.el7.x86_64", arch: "amd64", family: "unix"
Finished: SUCCESS
{code}

I reverted both plugins back to the previous version 1362.vee39a_d4b_02b_1 and the warning message is gone.

Does not look like a critical issue, but having the warning now with every invocation of withMaven() is very irritating for the users.

Rainer Montag made changes - 2024-01-08 09:50

Summary

Original: warning of unknown Maven version in plugin version 1368.vfb_8509d7b_869

New: pipeline-maven: warning of unknown Maven version in plugin version 1368.vfb_8509d7b_869

Rainer Montag made changes - 2024-01-08 09:51

Description

Original: After updating the pipeline-maven and pipeline-maven-api plugin from version 1362.vee39a_d4b_02b_1 to version 1368.vfb_8509d7b_869, I can now see every time withMaven() is invoked a warning message in the job log:
{code:java}
[withMaven] WARNING: You are running an old version of Maven (UNKNOWN), you should update to at least 3.8.x
{code}
But withMaven seems to pickup the correct Maven version despite the warning:

1) I have configured Maven tool "Maven 3.9.6" picking the version 3.9.6.

2) The following pipeline:
{code:java}
pipeline {
  agent { node { label 'linux' } }
stages {
    stage('Maven') {
steps {
withMaven(maven: "Maven 3.9.6") {
    sh "mvn -U -B -e -v"
   }
      }
}
}
}
{code}
creates the output
{code:java}
[withMaven] WARNING: You are running an old version of Maven (UNKNOWN), you should update to at least 3.8.x
+ mvn -U -B -e -v
Picked up JAVA_TOOL_OPTIONS: -Dmaven.ext.class.path="/srv/jenkins-data/node/workspace/DOT-1949-mvn@tmp/withMavenbbe509b0/pipeline-maven-spy.jar" -Dorg.jenkinsci.plugins.pipeline.maven.reportsFolder="/srv/jenkins-data/node/workspace/DOT-1949-mvn@tmp/withMavenbbe509b0"
Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
Maven home: /srv/jenkins-data/node/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.9.6
Java version: 17.0.9, vendor: Eclipse Adoptium, runtime: /usr/lib/jvm/temurin-17-jdk
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.10.0-1160.105.1.el7.x86_64", arch: "amd64", family: "unix"
Finished: SUCCESS
{code}

I reverted both plugins back to the previous version 1362.vee39a_d4b_02b_1 and the warning message is gone.

Does not look like a critical issue, but having the warning now with every invocation of withMaven() is very irritating for the users.

New: After updating the *pipeline-maven* and *pipeline-maven-api* plugin from version *1362.vee39a_d4b_02b_1* to version {*}1368.vfb_8509d7b_869{*}, I can now see every time withMaven() is invoked a warning message in the job log:
{code:java}
[withMaven] WARNING: You are running an old version of Maven (UNKNOWN), you should update to at least 3.8.x
{code}
But withMaven seems to pickup the correct Maven version despite the warning:

1) I have configured Maven tool "Maven 3.9.6" picking the version 3.9.6.

2) The following pipeline:
{code:java}
pipeline {
  agent { node { label 'linux' } }
stages {
    stage('Maven') {
steps {
withMaven(maven: "Maven 3.9.6") {
    sh "mvn -U -B -e -v"
   }
      }
}
}
}
{code}
creates the output
{code:java}
[withMaven] WARNING: You are running an old version of Maven (UNKNOWN), you should update to at least 3.8.x
+ mvn -U -B -e -v
Picked up JAVA_TOOL_OPTIONS: -Dmaven.ext.class.path="/srv/jenkins-data/node/workspace/DOT-1949-mvn@tmp/withMavenbbe509b0/pipeline-maven-spy.jar" -Dorg.jenkinsci.plugins.pipeline.maven.reportsFolder="/srv/jenkins-data/node/workspace/DOT-1949-mvn@tmp/withMavenbbe509b0"
Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
Maven home: /srv/jenkins-data/node/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.9.6
Java version: 17.0.9, vendor: Eclipse Adoptium, runtime: /usr/lib/jvm/temurin-17-jdk
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.10.0-1160.105.1.el7.x86_64", arch: "amd64", family: "unix"
Finished: SUCCESS
{code}

I reverted both plugins back to the previous version 1362.vee39a_d4b_02b_1 and the warning message is gone.

Does not look like a critical issue, but having the warning now with every invocation of withMaven() is very irritating for the users.

Rainer Montag added a comment - 2024-01-08 13:10

Running with traceability:true give some more information:

[withMaven] Options: []
[withMaven] Available options: 
[withMaven] using JDK installation provided by the build agent
[withMaven] using Maven installation 'Maven 3.9.6'
[withMaven] failed to read Maven version: Unable to serialize Optional[Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)]
[withMaven] WARNING: You are running an old version of Maven (UNKNOWN), you should update to at least 3.8.x
...

Rainer Montag added a comment - 2024-01-08 13:10 Running with traceability:true give some more information: [withMaven] Options: [] [withMaven] Available options: [withMaven] using JDK installation provided by the build agent [withMaven] using Maven installation 'Maven 3.9.6' [withMaven] failed to read Maven version: Unable to serialize Optional[Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)] [withMaven] WARNING: You are running an old version of Maven (UNKNOWN), you should update to at least 3.8.x ...

Valentin Delaye added a comment - 2024-01-08 14:34

Same issue here

[14:53:21.533+01:00] - [withMaven] failed to read Maven version: null
[14:53:21.533+01:00] - [withMaven] WARNING: You are running an old version of Maven (UNKNOWN), you should update to at least 3.8.x

But latest maven version is used on container (https://hub.docker.com/_/maven)

[14:53:22.935+01:00] - ----- withMaven Wrapper script -----
[14:53:22.935+01:00] - Picked up JAVA_TOOL_OPTIONS: -Dmaven.ext.class.path="/home/jenkins/agent/workspace/*********@tmp/withMavenf2a92218/pipeline-maven-spy.jar" -Dorg.jenkinsci.plugins.pipeline.maven.reportsFolder="/home/jenkins/agent/workspace/**********@tmp/withMavenf2a92218" 
[14:53:23.564+01:00] - Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
[14:53:23.565+01:00] - Maven home: /usr/share/maven

Valentin Delaye added a comment - 2024-01-08 14:34 Same issue here [14:53:21.533+01:00] - [withMaven] failed to read Maven version: null [14:53:21.533+01:00] - [withMaven] WARNING: You are running an old version of Maven (UNKNOWN), you should update to at least 3.8.x But latest maven version is used on container ( https://hub.docker.com/_/maven ) [14:53:22.935+01:00] - ----- withMaven Wrapper script ----- [14:53:22.935+01:00] - Picked up JAVA_TOOL_OPTIONS: -Dmaven.ext. class. path= "/home/jenkins/agent/workspace/*********@tmp/withMavenf2a92218/pipeline-maven-spy.jar" -Dorg.jenkinsci.plugins.pipeline.maven.reportsFolder= "/home/jenkins/agent/workspace/**********@tmp/withMavenf2a92218" [14:53:23.564+01:00] - Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae) [14:53:23.565+01:00] - Maven home: /usr/share/maven

Rainer Montag added a comment - 2024-01-10 08:50

bguerin can you have a look? It was introduced with https://github.com/jenkinsci/pipeline-maven-plugin/pull/749

Rainer Montag added a comment - 2024-01-10 08:50 bguerin can you have a look? It was introduced with https://github.com/jenkinsci/pipeline-maven-plugin/pull/749

Rainer Montag made changes - 2024-01-10 08:56

Link

New: This issue is caused by ~~JENKINS-72386~~ [ ~~JENKINS-72386~~ ]

Benoit made changes - 2024-01-24 21:13

Assignee

New: Benoit [ bguerin ]

Assignee:: Benoit

Reporter:: Rainer Montag

Votes:: 2 Vote for this issue

Watchers:: 6 Start watching this issue

Created:: 2024-01-08 08:59

Updated:: 2024-03-21 23:08

Jenkins

Details

Description

Attachments

Issue Links

Activity

Collapse comment: Rainer Montag added a comment - 2024-01-08 13:10

Expand comment: Rainer Montag added a comment - 2024-01-08 13:10

Collapse comment: Valentin Delaye added a comment - 2024-01-08 14:34

Expand comment: Valentin Delaye added a comment - 2024-01-08 14:34

Collapse comment: Rainer Montag added a comment - 2024-01-10 08:50

Expand comment: Rainer Montag added a comment - 2024-01-10 08:50

People

Dates