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

Maven Local Repository is always seen as relative when it should be absolute

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • pipeline-maven-plugin
    • None
    • Pipeline Maven Integration Plugin 3.6.7

      Using Jenkinsfile with

      withMaven(mavenLocalRepo: '${user.home}/.m2/$EXECUTOR_NUMBER/repository')

      resolves the local repository path to

      -Dmaven.repo.local=/home/jenkins/workspace/somerepository/${user.home}/.m2/2/repository: bad substitution

      so user.home does not get resolved. This is fine if not possible now. But also using

      withMaven(mavenLocalRepo: '~/.m2/$EXECUTOR_NUMBER/repository')
      resolves the local repository path to

      -Dmaven.repo.local=/home/jenkins/workspace/somerepository/~/.m2/2/repository

      Using
      withMaven(mavenLocalRepo: '$WORKSPACE/../../.m2/$EXECUTOR_NUMBER/repository')
      can be used to escape from a single non-permanent workspace to use a common local repository, but this is not ideal.

      Concerned code seems to be here:
      https://github.com/jenkinsci/pipeline-maven-plugin/blob/pipeline-maven-3.6.7/jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/WithMavenStepExecution2.java#L662

          [JENKINS-56232] Maven Local Repository is always seen as relative when it should be absolute

          Lasse Lindqvist added a comment -

          The related commit is here: https://github.com/jenkinsci/pipeline-maven-plugin/commit/496eb784e2e9a0fd9e463922f6001848c2d5eda6

          Lasse Lindqvist added a comment - The related commit is here: https://github.com/jenkinsci/pipeline-maven-plugin/commit/496eb784e2e9a0fd9e463922f6001848c2d5eda6

          Cyrille Le Clerc added a comment -

          Fixed in 3.6.10

          Cyrille Le Clerc added a comment - Fixed in 3.6.10

          Horst Krause added a comment -

          Note: The fix just checks if the mavenLocalRepo starts with a slash ("/") to detect absolute path. So using "~/.m2/any-repo-name" still won't work.

          Horst Krause added a comment - Note: The fix just checks if the mavenLocalRepo starts with a slash ("/") to detect absolute path. So using "~/.m2/any-repo-name" still won't work.

            cleclerc Cyrille Le Clerc
            lasselindqvist Lasse Lindqvist
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: