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

Full Folder support in naming Env variables

    Details

    • Similar Issues:

      Description

      Not sure (yet) who main culprit is, so adding both plugins.

      Current scenario is a multi-job setup, but since LAST_TRIGGERED_JOB_NAME comes from parameterized-trigger, adding them as well.

      When using env vars (ex: LAST_TRIGGERED_JOB_NAME) if the JOB_NAME is in a folder, rather than replace "/" with underscore, the name that gets derived is anything after that trailing slash.
      So if there's "Folder_A/Job_A" and "Folder_B/Job_A" there's going to be a problem if the value that LAST_TRIGGERED_JOB_NAME is returning is "Job_A".

        Attachments

          Activity

            People

            • Assignee:
              huybrechts huybrechts
              Reporter:
              brantone Brantone
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: