Features

Automatic setup of CI

Should be easy to take an IDE project, or project tree, or kenai.com workspace,
and set up a new CI job for it.

For a NB-generated Ant project, this means a freeform job
invoking build.xml with the test target,
collecting dist/*.jar and test result artifacts.

For a freeform or automatic Ant project, this may not be possible without user intervention.

For a Maven project (possibly consisting of multiple modules),
this would be best handled by using Hudson's native Maven 2 support.
The IDE should also populate the CI field in pom.xml.

Setup of Rails projects is TBD.

There is no Rails job type in Hudson currently. Could be created if useful.

Are any artifacts necessary, or is the source tree itself enough to deploy?

How to present test results in a way that Hudson can display? Should they be converted to Ant JUnit XML format, or does Hudson need an SPI for loading test results?

Monitoring and control

Basic monitoring and control from the IDE,
along the lines of what the current module does but more polished:
see running builds,
get unobtrusive notifications when a build fails
(especially if you are listed in the changelog!),
maybe start or cancel builds,
and of course jump to the main Hudson interface in a web browser
for anything not better supported inside the IDE.

Changelog and source review

Ability to review build's changelog using IDE's diff viewer;
maybe to switch workspace to VCS snapshot represented by build.
Ability to browse job's workspace remotely using a tree view in the IDE (and open files R/O).