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

Support expanding environment variables

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • cobertura-plugin
    • Jenkins ver. 1.613
      Jenkins Cobertura Plugin 1.9.7

      Add support for expanding environment variables - when injecting variables to build process using "inject environment variables to build process" option I'd like to be able to use them in "Cobertura xml report pattern" field i.e.: $PROJECT_HOME/target/cobertura-coverage.xml. This feature is supported by most of other report plugins (i.e. JUnit reporter plugin).

          [JENKINS-30647] Support expanding environment variables

          Bartosz Kaczorek created issue -
          Bartosz Kaczorek made changes -
          Description Original: Add expanding of environment variables - when injecting variables to build process using "inject environment variables to build process" option I'd like to be able to use them in "Cobertura xml report pattern" field i.e.: $PROJECT_HOME/target/cobertura-coverage.xml. This feature is supported by most of other report plugins (i.e. JUnit reporter plugin).
          		 New: Add support for expanding environment variables - when injecting variables to build process using "inject environment variables to build process" option I'd like to be able to use them in "Cobertura xml report pattern" field i.e.: $PROJECT_HOME/target/cobertura-coverage.xml. This feature is supported by most of other report plugins (i.e. JUnit reporter plugin).
          Issue Type Original: New Feature [ 2 ] New: Improvement [ 4 ]
          Summary Original: Expand environment variables New: Support expanding environment variables
          Bartosz Kaczorek made changes -
          Labels New: cobertura jenkins

          Jan Vrany added a comment - - edited

          I second that. My use case is following: I have a job that does incremental builds, i.e., multiple builds share the same workspace
          (which is cleanded every night to make sure it builds from scratch).
          The Cobertura results .xml files (as well as Junit result .xml files) has Jenkins BUILD_NUMBER in it. I need to use pattern like

          reports/*mercurial*build${BUILD_NUMBER}*Coverage.xml

          to match coverage reports.

          Jan Vrany added a comment - - edited I second that. My use case is following: I have a job that does incremental builds, i.e., multiple builds share the same workspace (which is cleanded every night to make sure it builds from scratch). The Cobertura results .xml files (as well as Junit result .xml files) has Jenkins BUILD_NUMBER in it. I need to use pattern like reports/*mercurial*build${BUILD_NUMBER}*Coverage.xml to match coverage reports.

          Stephen Connolly added a comment -

          Last two releases (separated by over a year) were by olivergondza so looks like the maintainer

          Stephen Connolly added a comment - Last two releases (separated by over a year) were by olivergondza so looks like the maintainer
          Stephen Connolly made changes -
          Assignee Original: Stephen Connolly [ stephenconnolly ] New: Oliver Gondža [ olivergondza ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 165762 ] New: JNJira + In-Review [ 182126 ]

          Alexandre Charvier added a comment -

          Hello,

          Are there any news on this topic? Will it be possible to use environment variables for junit reports configuration (XMLs location)

          Alex.

          Alexandre Charvier added a comment - Hello, Are there any news on this topic? Will it be possible to use environment variables for junit reports configuration (XMLs location) Alex.
          Oliver Gondža made changes -
          Assignee Original: Oliver Gondža [ olivergondza ]

          spam me added a comment -

          I have the same issue, I would like to use environment variables for the report path, but it doesn't work. 

          spam me added a comment - I have the same issue, I would like to use environment variables for the report path, but it doesn't work. 

            Unassigned Unassigned
            bartoszkaczorek Bartosz Kaczorek
            Votes:
            4 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: