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

injectedEnvVars Environment variables missing "Workspace"

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • envinject-plugin
    • None
    • docker based, 2.19.2

      Using jenkins 2.19.2 (or 2.19.4, through official docker image), with envinject, Environment Injector Plugin 1.93.1.
      Doing an empty "freestyle" job build and on the result cheking out the environment-Variables page (i.e. http://192.168.99.100:8080/job/test/2/injectedEnvVars/) will not show the "Workspace" variable.
      Also not included when using the REST-API (i.e. http://192.168.99.100:8080/job/test/2/injectedEnvVars/api/json?pretty=true).

      It IS however set (tested via "execute shell" -> printvars).

      After activating the "Inject environment variables to the build process" in the job configuration (even without setting anything), the Workspace variable shows up in the results.

        1. complete.png
          complete.png
          46 kB
        2. missing.png
          missing.png
          45 kB

          [JENKINS-40411] injectedEnvVars Environment variables missing "Workspace"

          Oleg Nenashev added a comment -

          Unfortunately I will not have time to work on EnvInject issues for a while. I decided to unassign all issues so that somebody can take them and finalize.

          Context: The plugin has been waiting for adoption for ~2 years. During all this time I was trying to keep this plugin afloat by reviewing the incoming pull requests, fixing defects and keeping the codebase up to date to simplify the handover. But I have not been using this plugin on my own so that such maintenance was a bit lame. I invite all active users to contribute to the plugin by taking ownership of this plugin and of EnvInject API. I am happy to provide any required knowledge transfers and do some assistance during the first months of maintenance

          Oleg Nenashev added a comment - Unfortunately I will not have time to work on EnvInject issues for a while. I decided to unassign all issues so that somebody can take them and finalize. Context: The plugin has been waiting for adoption for ~2 years. During all this time I was trying to keep this plugin afloat by reviewing the incoming pull requests, fixing defects and keeping the codebase up to date to simplify the handover. But I have not been using this plugin on my own so that such maintenance was a bit lame. I invite all active users to contribute to the plugin by taking ownership of this plugin and of EnvInject API. I am happy to provide any required knowledge transfers and do some assistance during the first months of maintenance

            Unassigned Unassigned
            afe Andreas Fe
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: