Ability to set output of a step to environment variable(s)

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

XMLWordPrintable

      When using steps like input that capture data from a user, it makes sense to be able to set the resultant values to environment variables.

      This could be generalised to other steps that return values (perhaps as maps).

      In pipeline-model, the way data is passed around is via (environment) variables as there are no local variables, so the ability to set environment variables to the output is required.

            Assignee:
            Andrew Bayer
            Reporter:
            Michael Neale
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: