CommandInterpreter return value fix: causes incompatibility with Env-inject plugin in Jenkins v2.26

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      When running Jenkins 2.26 with envinject-plugin and returning a map object from an Evaluated Groovy script, the environment variables are created but are empty.

      If I downgrade to Jenkins 2.25 environment variables are set correctly. Appears something in 2.26 breaks this plugin.

            Assignee:
            Unassigned
            Reporter:
            Andrew Gray
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: