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

Reduce noisy logs when using withMaven inside a Docker container

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      withMaven issues the following warning message when used in a container:

      [withMaven] WARNING: "withMaven(){...}" step running within a container. Since the Docker Pipeline Plugin version 1.14, you MUST:
[withMaven] * Either prepend the 'MVN_CMD_DIR' environment variable to the 'PATH' environment variable in every 'sh' step that invokes 'mvn' (e.g. "sh 'export PATH=$MVN_CMD_DIR:$PATH && mvn clean deploy' ").
[withMaven] * Or use 'MVN_CMD' instead of invoking 'mvn'" (e.g. \"sh \'$MVN_CMD clean deploy\' \").
[withMaven] * Or use Takari's Maven Wrapper (e.g. "sh './mvnw clean deploy'")
[withMaven] See "Pipeline Maven Plugin FAQ"

      This message is frightening and way too verbose if the pipeline properly integrates withMaven with "docker.image("...").inside{...}"

        Attachments

          Activity

          Ascending order - Click to sort in descending order
          cleclerc Cyrille Le Clerc created issue -
          cleclerc Cyrille Le Clerc made changes -
          Field Original Value New Value
          Description withMaven issues the following warning message when used in a container:

          {noformat}
          [withMaven] WARNING: "withMaven(){...}" step running within a container. Since the Docker Pipeline Plugin version 1.14, you MUST:
          [withMaven] * Either prepend the 'MVN_CMD_DIR' environment variable to the 'PATH' environment variable in every 'sh' step that invokes 'mvn' (e.g. "sh 'export PATH=$MVN_CMD_DIR:$PATH && mvn clean deploy' ").
          [withMaven] * Or use 'MVN_CMD' instead of invoking 'mvn'" (e.g. \"sh \'$MVN_CMD clean deploy\' \").
          [withMaven] * Or use Takari's Maven Wrapper (e.g. "sh './mvnw clean deploy'")
          [withMaven] See "Pipeline Maven Plugin FAQ"
          {noformat}

          This message is frightening and way too verbose if the pipeline properly integrates withMaven with "docker.image("...").inside{...}"
          		 withMaven issues the following warning message when used in a container:

          {noformat}
          [withMaven] WARNING: "withMaven(){...}" step running within a container. Since the Docker Pipeline Plugin version 1.14, you MUST:
          [withMaven] * Either prepend the 'MVN_CMD_DIR' environment variable to the 'PATH' environment variable in every 'sh' step that invokes 'mvn' (e.g. "sh 'export PATH=$MVN_CMD_DIR:$PATH && mvn clean deploy' ").
          [withMaven] * Or use 'MVN_CMD' instead of invoking 'mvn'" (e.g. \"sh \'$MVN_CMD clean deploy\' \").
          [withMaven] * Or use Takari's Maven Wrapper (e.g. "sh './mvnw clean deploy'")
          [withMaven] See "Pipeline Maven Plugin FAQ"
          {noformat}

          This message is frightening and way too verbose if the pipeline properly integrates withMaven with "docker.image("...").inside\{...\}"
          Hide
          Permalink
          cleclerc Cyrille Le Clerc added a comment -

          Fixed in 3.6.10

          Show
          cleclerc Cyrille Le Clerc added a comment - Fixed in 3.6.10
          cleclerc Cyrille Le Clerc made changes -
          Resolution Fixed [ 1 ]
          Status Open [ 1 ] Closed [ 6 ]

            People

            Assignee:
            cleclerc Cyrille Le Clerc
            Reporter:
            cleclerc Cyrille Le Clerc
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: