Proper method of saving output from a plugin

[Christian McHugh]

Greetings,

The saltstack plugin sends a message to the saltapi, and returns the response to the Jenkins console. With the introduction of scripted pipelines, it is now possible to return the result into a groovy variable for further processing. For older freestyle jobs however, that is not an option, so the plugin currently allows for saving the saltapi output as an environment variable to again allow for further processing in subsequent shell steps.

However there is a problem if the saltapi returns are large amount of data, which results in an error when attempting to save it into an environment variable. What are the recommendations for supporting large environment variables? Currently this process is implemented as discussed here, however the EnvironmentContributingAction appears to eventually shell out, resulting in the mentioned error when passed a large chunk of data.

Thanks!

[Daniel Beck]

> On 20.04.2017, at 08:04, Christian McHugh <christia...@gmail.com> wrote:
>
> For older freestyle jobs however, that is not an option, so the plugin currently allows for saving the saltapi output as an environment variable to again allow for further processing in subsequent shell steps.

Why not write to a file instead?

[Ted Xiao]

you can also extend InvisibleAction and add it to the build

Run.addAction

Run.getAction

[Christian McHugh]

To close this out, went with the write a file solution.

Thanks all