Due to some maintenance issues, this service has been switched in read-only mode, you can find more information about the why

and how to migrate your plugin documentation in this blogpost

Skip to end of metadata
Go to start of metadata

Plugin Information

View Asynchronous Job type on the plugin site for more information.

Library plugin for custom job types that model external asynchronous processes

This is a library plugin, meaning it doesn't expose user-visible features by itself. Instead, it's meant to be used by other plugins as a dependency.

This plugin defines the AsyncJob/AsyncRun classes, which are abstract subtypes of Job and Run. These subtypes are convenient for modeling asynchronous executions that are happening outside Jenkins. Unlike AbstractBuild, where the duration of a build is tied to a life of an Executor thread, the completion of AsyncBuild is set by invoking a callback AsyncBuild.markCompleted(). Because of this, a AsyncBuild can stay in the "building" state across Jenkins restarts.

To make this extension possible, we bend Jenkins core a bit. As far as the core is concerned, AsyncBuild completes right away, but it fakes various state retrieval getter methods to make it look like it's still in progress. This will likely confuse some other plugins, but we hope to improve this faking as we go.

See TestAsyncJob and TestAsyncRun in the src/test/java for an example of how to use this plugin. To test it in action, run mvn -Dtest=Main test, wait for the line "Started SocketConnector@" to appear, and then open http://localhost:8888/


Version 1.0 (Oct 26, 2012)

  • Initial release
  • No labels

1 Comment

  1. Unknown User (josesa)

    Great! Would that mean we could have AsyncJobs for running long regression tests (several hours) that would survive Jenkins restart?

    Sometimes restart is unavoidable unfortunately either due to locks that stay forever (JENKINS-9688) or CPU going 100% (JENKINS-14362)