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.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
- 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