Hi, thanks for batch-task!

We use batch tasks for deploying code to servers after it is built. Typically,
the task copies files to a server or several, and (in some cases ) bounces the
applications.

Hudson's ability to keep up with artifacts is nice-- it means that if we keep up
with them for old builds, we have what we need to very easily put an older
version of an application into any environment we choose. this is very nice for
when we need to troubleshoot a problem report based on an older version.

Unfortunately, there does not appear to be a way to run a batch task on an old
build, so we can access the artifacts, but we cannot deploy them using our batch
tasks.

What would be nice is if it were possible to run a batch task on an old build.

Current Behavior:

• Configure a batch task that copies a file or two somewhere.
• Run a build, call it build #1. observe that batch tasks can be run on that
  project, using the "Tasks" link
• Run another build, call it build #2. observe that you can see tasks run on
  that build "Executed TAsks", but cannot run any new ones.

Desired Behavior:

• Configure a batch task that copies a file or two somewhere
• run a build, call it build #1. the "tasks" link can be used to run tasks
  and see those that have been run already
• run another build, call it build #2, the "tasks" link is still visible, and
  allows display of ones already run, and allows running new ones in the way the
  current build works.

If necessary, it would be fine to assume that batch tasks run on builds not the
current build have access only to archived artifacts. Our use case is that our
build produces a set of war files, so the batch tasks need access only to those
files.