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

XMLWordPrintable

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major
    • Component/s: memory-map-plugin
    • None
    • Environment:
      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.

            Assignee:
            Praqma Support
            Reporter:
            Bue Petersen
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: