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

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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Duplicate
    • Component/s: memory-map-plugin
    • Labels:
      None
    • Environment:
      Master and slaves on Linux, Jenkins 1.491
    • Similar Issues:

      Description

      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.

        Attachments

          Activity

          Hide
          bue Bue Petersen added a comment -

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

          Show
          bue Bue Petersen added a comment - We now only use github issues, continue in https://github.com/Praqma/memory-map-plugin/issues/28

            People

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

              Dates

              Created:
              Updated:
              Resolved: