On Tuesday, May 30, 2017 at 2:40:36 PM UTC+1, Jesse Glick wrote: > > You may not use `newBodyInvoker` on a step that does not take a body > (~ closure argument). > Understood
> Did you look at `SleepStep` for an example? Or `InputStep`? > Yes. The difficulty I'm running into is that there are multiple possible http calls, only one of which is long running and requires subsequent polling for status. Thus, my long running process is sort of monolithic and different from something like SleepStep that can initiate the command in the start() and later check in at onResume(). In my case I'd really like to kick off the http call in start(), but just don't want it killed off/hogging the start() thread. In looking around, I came across a method of doing just as described by running the http process in it's own thread and worked up the following version: https://github.com/jenkinsci/saltstack-plugin/pull/95 This seems to work as intended, but now I have a problem where previously I was using AbstractSynchronousStepExecution and the run() method returned a string. Now with the new thread process, I don't think I can return a String. Any ideas for being able to return a String from AbstractStepExecutionImpl? -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/29b34b5e-fd02-4737-a5ed-9c4dd484b6e6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
