Re: How can a plugin save output when running in pipeline

2017-01-05 Thread Jesse Glick
On Mon, Dec 26, 2016 at 4:13 PM, Christian McHugh wrote: > I'm a bit stuck on the conversion of SimpleBuildStep to full step needed to > have the pipeline syntax be able to return output to be saved into a > variable. > As I'm not a jenkins framework expert by any means, would anyone be able to >

Re: How can a plugin save output when running in pipeline

2016-12-26 Thread Christian McHugh
Hey everyone/Jesse, Thanks for all of your assistance and pointers thus far! In the currently released pre-pipeline version, this plugin was capable of performing its own variable substitution to read in existing environment variables as well as export the return into an envvar for further proces

Re: How can a plugin save output when running in pipeline

2016-12-06 Thread Jesse Glick
On Tue, Dec 6, 2016 at 1:26 AM, Christian McHugh wrote: > Can you advice on how to get > https://github.com/jenkinsci/saltstack-plugin/blob/master/src/main/java/com/waytta/SaltAPIBuilder.java#L217 > this returnArray.toString() variable exported in a pipeline job? You can return a value from a `S

Re: How can a plugin save output when running in pipeline

2016-12-05 Thread Christian McHugh
Hey Jesse, I've been fiddling with this off and on, but I'm not making any progress. Can you advice on how to get https://github.com/jenkinsci/saltstack-plugin/blob/master/src/main/java/com/waytta/SaltAPIBuilder.java#L217 this returnArray.toString() variable exported in a pipeline job? Thanks

Re: How can a plugin save output when running in pipeline

2016-11-07 Thread Jesse Glick
On Thu, Nov 3, 2016 at 7:31 PM, Christian McHugh wrote: > Does anyone have a recommendation or example for how to save output of a > plugin into a variable when running as a pipeline job? `PwdStep` shows the simplest example I can think of. -- You received this message because you are subscribe

How can a plugin save output when running in pipeline

2016-11-03 Thread Christian McHugh
Does anyone have a recommendation or example for how to save output of a plugin into a variable when running as a pipeline job? Currently, the saltstack plugin uses listener.getLogger().println() to display output. However this is not to be saved