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

Jenkins variables are not expanded in Coverity plugin

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Minor Minor
    • coverity-plugin

      In the additional arguments fields for cov-build, cov-analyze, cov-commit, etc., Jenkins build variables are not able to be used. I tried to add the following to additional cov-commit-defects arguments:

      --strip-path "${WORKSPACE}" --target x86 --description "from Jenkins"

      and the variable is not replaced with the workspace, it actually tried to strip the path of '${WORKSPACE}' which is obviously not what you want to do.

          [JENKINS-14833] Jenkins variables are not expanded in Coverity plugin

          Kyle O'Connor created issue -
          Kyle O'Connor made changes -
          Labels New: plugins windows

          Victor Martinez added a comment -

          + 1.

          Another example:

          $ /usr/local/coverity5/bin/cov-commit-defects --dir /storage/jenkins/coverity/TLINKSERVER_MAINLINE_COVERITY --host coverity55 --port 8080 --stream tlinkserver_trunk --user admin --description ${BUILD_TAG}

          "${BUILD_TAG}" is a global variable

          Victor Martinez added a comment - + 1. Another example: $ /usr/local/coverity5/bin/cov-commit-defects --dir /storage/jenkins/coverity/TLINKSERVER_MAINLINE_COVERITY --host coverity55 --port 8080 --stream tlinkserver_trunk --user admin --description ${BUILD_TAG} "${BUILD_TAG}" is a global variable

          Brett Delle Grazie added a comment -

          +1
          --strip-path ${WORKSPACE}
          or similar is extremely useful when using nodes with differing paths

          Brett Delle Grazie added a comment - +1 --strip-path ${WORKSPACE} or similar is extremely useful when using nodes with differing paths

          Drew Reed added a comment -

          I believe I've just sent a pull request on github for a patch that addresses this problem

          Drew Reed added a comment - I believe I've just sent a pull request on github for a patch that addresses this problem
          Chris Wozny made changes -
          Link New: This issue is blocking JENKINS-18551 [ JENKINS-18551 ]

          Chris Wozny added a comment -

          Can we get an update as to whether this has been brought in yet? Also, I wonder if it would be possible to maintain a backported 1.2.4 branch for the folks who aren't using CIM v6 or greater...

          Chris Wozny added a comment - Can we get an update as to whether this has been brought in yet? Also, I wonder if it would be possible to maintain a backported 1.2.4 branch for the folks who aren't using CIM v6 or greater...
          Daniel Fischer made changes -
          Labels Original: plugins windows New: linux plugins windows

          Daniel Fischer added a comment -

          Our Java build slaves are running on multiple platforms. We would like to reuse the intermediate directories to speed up the Java incremental builds (between ALL platforms).

          The intermediate directories are shared over a network filesystem (CIFS and NFS).
          The nodes have an environment variable "coverityimdirs" set to the directory of the shared mount point (mapped CIFS shareon windows and mounted NFS share on linux).

          If I could use the node environment variables here all would be fine.

          I have already tried "$coverityimdirs", "${coverityimdirs}" and "${ENV.coverityimdirs}".
          In any case the coverity plugin does not replace the variable with the value I have set on the node environment.

          Daniel Fischer added a comment - Our Java build slaves are running on multiple platforms. We would like to reuse the intermediate directories to speed up the Java incremental builds (between ALL platforms). The intermediate directories are shared over a network filesystem (CIFS and NFS). The nodes have an environment variable "coverityimdirs" set to the directory of the shared mount point (mapped CIFS shareon windows and mounted NFS share on linux). If I could use the node environment variables here all would be fine. I have already tried "$coverityimdirs", "${coverityimdirs}" and "${ENV.coverityimdirs}". In any case the coverity plugin does not replace the variable with the value I have set on the node environment.

          Roger Layani added a comment -

          Is there any plan to implement this capability?
          It is very important for the plugin usage.

          Roger Layani added a comment - Is there any plan to implement this capability? It is very important for the plugin usage.

            joshvinson Josh Vinson
            koconnor Kyle O'Connor
            Votes:
            9 Vote for this issue
            Watchers:
            17 Start watching this issue

              Created:
              Updated:
              Resolved: