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

EnvInject 1.40 does not resolve anymore environment variables in values of environment variables

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: envinject-plugin
    • Labels:
      None
    • Environment:
      Windows Server 2008, Jenkins 1.456. List of plugins attached.
    • Similar Issues:

      Description

      Most of our jobs had EnvInject variables like the following:
      DATABASE_NAME=JenkinsFooBar${SVN_REVISION}

      These were happily resolved until we upgraded EnvInject from 1.00 to 1.40, and Jenkins itself from 1.435 to 1.456. After the upgrade, EnvInject logs an error saying that variable DATABASE_NAME is unresolved.

        Attachments

          Activity

          gabrielegiuseppini Gabriele Giuseppini created issue -
          gbois Gregory Boissinot made changes -
          Field Original Value New Value
          Status Open [ 1 ] In Progress [ 3 ]
          gabrielegiuseppini Gabriele Giuseppini made changes -
          Attachment config.xml [ 21668 ]
          gbois Gregory Boissinot made changes -
          Status In Progress [ 3 ] Resolved [ 5 ]
          Resolution Fixed [ 1 ]
          rtyler R. Tyler Croy made changes -
          Workflow JNJira [ 143647 ] JNJira + In-Review [ 190657 ]

            People

            • Assignee:
              gbois Gregory Boissinot
              Reporter:
              gabrielegiuseppini Gabriele Giuseppini
            • Votes:
              1 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: