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

Environment variables can not be used in filepaths (Praqma case 9430)

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • memory-map-plugin
    • None
    • Master and slaves on Linux, Jenkins 1.491

      For example using the following path for in the Linker Command File: ${GIT_CLONE_DIR}/${cmdfile}-${BCONF}.cmd

      ... can't be found.

      Using the same path in for example Archive Artifacts will work, thus the env. vars. are available in the post-build step.

          [JENKINS-18176] Environment variables can not be used in filepaths (Praqma case 9430)

          Bue Petersen created issue -
          Bue Petersen made changes -
          Summary Original: Environment variables can not be used in filepaths New: Environment variables can not be used in filepaths (Praqma case 9430)
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 149474 ] New: JNJira + In-Review [ 177373 ]

          Bue Petersen added a comment -

          We now only use github issues, continue in https://github.com/Praqma/memory-map-plugin/issues/28

          Bue Petersen added a comment - We now only use github issues, continue in https://github.com/Praqma/memory-map-plugin/issues/28
          Bue Petersen made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]

            praqma Praqma Support
            bue Bue Petersen
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: