Re: Starting an asynchronous step

On Fri, Apr 6, 2018 at 10:30 AM, Jeff Wilson wrote: > I can't find a (canonical) example -- does anyone > have a pointer to such? The `sleep` step is probably the simplest to understand. The most relevant bits:

Re: Starting an asynchronous step

In this example, the important parts are in the setUpTimer() method, as are as follows: task = Timer.get().schedule(new Runnable() { @Override public void run() { getContext().onSuccess(null); } }, end - now, TimeUnit.MILLISECONDS); So, we basically handle our own multi-threading in

Re: Starting an asynchronous step

On Fri, Apr 6, 2018 at 4:48 PM, Jeff Wilson wrote: > So, we basically handle our own multi-threading in the start() command, as > in this example? Yes, it is an asynchronous API—the Pipeline runtime tells your step when to start, and you tell it when it is finished. What

Request to be made a maintainer of audit-trail-plugin

Hello, I request to be made a maintainer of audit-trail-plugin. Now this repository is abandon. Cheers, Tomasz -- 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

Re: Taking over maintenance for fitnesse plugin

Michaël, I am also interested in helping maintain the fitnesse plugin. I'm currently looking at what it will take to turn it into a pipeline-aware plugin, but I am a neophyte at plugin development. Let me know if you want me to help in anyway. On Monday, March 26, 2018 at 1:47:12 PM UTC-4,

Re: [Essentials] RFC: first cut at registration and authentication for Jenkins Essentials

Just a heads up to any of those interested, the pull requests implemneting this functionality, described in JEP-303 (https://github.com/jenkinsci/jep/tree/master/jep/303) can be found here: * Registration component: https://github.com/jenkins-infra/evergreen/pull/37 * Login component:

Starting an asynchronous step

I'm trying to write a new pipeline plugin for a build step that is long-running and prone to network delays and timeouts, so it would appear that an asynchronous step is the best way to implement this. However, I have questions about how to implement the StepExecution.start() method to start

Re: Starting an asynchronous step

Perhaps you've already read this guide? https://github.com/jenkinsci/workflow-step-api-plugin/blob/master/README.md#creating-an-asynchronous-step /B 2018-04-06 16:30 GMT+02:00 Jeff Wilson : > I'm trying to write a new pipeline plugin for a build step that is >

Re: Starting an asynchronous step

Indeed. It simply says to implement the start() method as needed. There are no examples of what an implementation might look like, nor is there a description/documentation of what to do. On Friday, April 6, 2018 at 12:12:47 PM UTC-4, Robert Sandell wrote: > > Perhaps you've already read this