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

Provide a short $JOB_NAME inside a folder

    XMLWordPrintable

    Details

    • Similar Issues:
    • URL:

      Description

      We are using $JOB_NAME a lot to automatically create names für ClearCase views in our jobs. This looks like

      ${USER_NAME}${COMPUTERNAME}${JOB_NAME} for the view tag and
      ${JOB_NAME} for the view name.

      Additionaly we ha a small managed script to automatically create a build tag:
      echo %BUILD_TAG% > %CLEARCASE_VIEWPATH%%JOB_NAME%-build.tag

      When a Job is now moved into a folder the JOB-NAME is "foldername/jobname" which is longer and contains a slash causing real pain on windows.

      I don't know if someone is relying on JOB_NAME containing the folder name and the slash, but would it be possible to separate this into two variables like FOLDER_NAME and (SHORT_)JOB_NAME?

        Attachments

          Activity

          Ascending order - Click to sort in descending order
          7 older comments
          Hide
          Permalink
          allan_burdajewicz Allan BURDAJEWICZ added a comment -

          The EnvInject plugin gives access to currentJob instance and therefore it is possible to inject the "short" job name like this:

          return ['ITEM_NAME': currentJob.getName()]
          Show
          allan_burdajewicz Allan BURDAJEWICZ added a comment - The EnvInject plugin gives access to currentJob instance and therefore it is possible to inject the "short" job name like this: return [ 'ITEM_NAME' : currentJob.getName()]
          Hide
          Permalink
          teilo James Nord added a comment -

          It should be trivial to implement this in a plugin. see buildtagfixer for an approach that fixed the BUILD_TAG environment variable to contain the full job name when folders where first introduced.

          Show
          teilo James Nord added a comment - It should be trivial to implement this in a plugin. see buildtagfixer for an approach that fixed the BUILD_TAG environment variable to contain the full job name when folders where first introduced.
          Hide
          Permalink
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Felix Belzunce Arcos
          Path:
          core/src/main/java/hudson/model/Job.java
          core/src/main/resources/jenkins/model/CoreEnvironmentContributor/buildEnv.groovy
          core/src/main/resources/jenkins/model/CoreEnvironmentContributor/buildEnv.properties
          http://jenkins-ci.org/commit/jenkins/4bab3630efcc2fa331db2989e321d9af1b8cdc1c
          Log:
          [FIXED JENKINS-25164] Add JOB_BASE_NAME env var (#2321)

          • Delete strip off
          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Felix Belzunce Arcos Path: core/src/main/java/hudson/model/Job.java core/src/main/resources/jenkins/model/CoreEnvironmentContributor/buildEnv.groovy core/src/main/resources/jenkins/model/CoreEnvironmentContributor/buildEnv.properties http://jenkins-ci.org/commit/jenkins/4bab3630efcc2fa331db2989e321d9af1b8cdc1c Log: [FIXED JENKINS-25164] Add JOB_BASE_NAME env var (#2321) JENKINS-25164 Add SHORT_JOB_NAME env var Delete strip off JENKINS-25164 Change SHORT_JOB_NAME for LEAF_JOB_NAME JENKINS-25164 Change LEAF_JOB_NAME for JOB_BASE_NAME
          Hide
          Permalink
          oleg_nenashev Oleg Nenashev added a comment -

          Released as Jenkins-2.4

          Show
          oleg_nenashev Oleg Nenashev added a comment - Released as Jenkins-2.4
          Hide
          Permalink
          djviking Sverre Moe added a comment -

          Not sure if it is intentional
          With Jenkins pipeline the JOB_BASE_NAME is same as BRANCH_NAME instead of the actual project name.
          BRANCH_NAME=master
          JOB_NAME=projectA/master
          JOB_BASE_NAME=master

          The value for JOB_BASE_NAME should be in this case projectA.

          Show
          djviking Sverre Moe added a comment - Not sure if it is intentional With Jenkins pipeline the JOB_BASE_NAME is same as BRANCH_NAME instead of the actual project name. BRANCH_NAME=master JOB_NAME=projectA/master JOB_BASE_NAME=master The value for JOB_BASE_NAME should be in this case projectA.

            People

            Assignee:
            fbelzunc Félix Belzunce Arcos
            Reporter:
            bruce Dirk Kuypers
            Votes:
            2 Vote for this issue
            Watchers:
            9 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: