On Fri, Nov 25, 2016 at 4:14 AM, Julien HENRY <[email protected]> wrote: > I found this ticket https://issues.jenkins-ci.org/browse/JENKINS-27127 that > is really close to what we need.
Yes, sounds like it. The issue needs to be “defuzzed” somewhat: concrete proposals written up, possibly broken into multiple features. > Is there any progress on that topic? Not currently. > Waiting for this generic step, do you think it would be possible to > implement the feature with a custom step? Sure, there is nothing stopping you from writing a limited version of this feature tailored to your needs. https://github.com/jenkinsci/workflow-step-api-plugin/#creating-an-asynchronous-step plus probably an `UnprotectedRootAction` (take care to consider malicious payloads). -- 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/CANfRfr0eoqDrV_sMtvN7XR3aPExECjwki4Ckzqg8O93HLKL08A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
