Re: Proper method of saving output from a plugin

[Christian McHugh]

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

Thanks all

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/4f219927-fca3-4f3a-a6fa-8a3ab52030af%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proper method of saving output from a plugin

[Ted Xiao]

you can also extend InvisibleAction and add it to the build

Run.addAction
Run.getAction


On Thursday, April 20, 2017 at 2:04:03 PM UTC+8, Christian McHugh wrote:
>
> 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!
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/21e68a7b-e5c3-4d8b-9f2b-9bd81d82914b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proper method of saving output from a plugin

[Daniel Beck]

> On 20.04.2017, at 08:04, Christian McHugh  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?

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/97FE46C4-8A34-422E-8A90-45874799881C%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.