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

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 28 Next »

Plugin Information

View batch task on the plugin site for more information.

This plugin adds batch tasks that are not regularly executed to projects, such as releases, integration, archiving, etc. In this way, anyone in the project team can execute them in a way that leaves record.


When you install this plugin, your project configuration page gets additional "batch tasks" option as illustrated below:

A batch task consists of a shell script and a name. When you execute a build, the shell script gets run on the workspace, just like a build. Batch tasks and builds "lock" the workspace, so when one of those activities is in progress, all the others will block in the queue.
Once a task is configured, the project top page gets "task(s)" link, as illustrated below:

If you click that, you can see the status of all the tasks. You can schedule the execution of a task from here, too. Task executions are numbered like "123-456" where 123 portion refers to the latest build and 456 portion refers to the sequential number (so that you can execute a task multiple times with the same build.) The build number portion is significant because when a batch task runs, it sees the workspace as of the result of this build.

The details of the task execution and its console output are available by further clicking a task of the interest, as below:


Version 1.11 (2010/01/03)

Version 1.10 (2009/12/07)

  • A few minor bug fixes.

Version 1.9 (2009/11/05)

  • Add "trigger even if build is unstable" selector for invoking tasks as a post-build action. Previously the tasks were always invoked (even for failed builds); now they will only run if the build result meets the required threshold (and never for failed builds).
  • Fix build number written to job log when task is invoked as a post-build action (was off by one)
  • Fix broken image for aborted task (grey ball)
  • On task page, show only builds for this task in Build History (instead of all tasks)
  • Avoid error if try to run a task when there are no builds for the project

Version 1.8 (2009/08/28)

  • Improved the error diagnosis and recovery when a build no longer has a workspace (report) – requires Hudson 1.319 or higher.

Version 1.7 (2009/03/31)

  • Allow non-admin users ability to manage and execute tasks (JENKINS-1198)

Version 1.6 (2009/02/27)

  • Updated to work with recent versions of Hudson (JENKINS-3173)

Version 1.5 (2009/01/27)

  • Fixed a bug "batchtask in queue causes NPE at startup" (JENKINS-2925)

Version 1.3 (2008/01/29)

  • Updated to work with the latest version of Hudson, so that it won't cause AbstractMethodError (report)
  • Last successful/failed builds were computed incorrectly (JENKINS-1012)
  • Icon size in task list is now configurable (JENKINS-1010)

Version 1.2 (2007/11/16)

  • Task can be now individually deleted from the left menu
  • Build number should start from 1 (JENKINS-991)
  • Tasks now work on Windows (JENKINS-985)
  • Build icon in task list is not larger than the other icons (JENKINS-1010)

Version 1.0 (2007/10/18)

  • initial version
  • No labels