The following items have been moved from the WishList:
How about linking to this site from the CruiseControl web pages and packaged documentation? The "official" docs are IMO rather weak (though much improved from the last time I investigated CC).
Done.
We use cvs to cm or projects, we have a concept of latest workspace, which currently gets updated using a cron. It would be good if an additional attribute could be added to update localworkingcopy before the ant task is scheduled. This would allow us to remove the cron and have CruiseControl take responsiblity for maintaining the latest.
We could fudge this by having the ant task update latest, this would work fine as long as it was not build.xml that was being updated.
DamianOneill
CVSBootstrapper can now optionally update a project instead of just one file. This fix is in CVS, not CC 2.0.2 [But is in CC 2.1 and up]
Two issues that have been much discussed on the mailing lists:
- support for multiple projects in the config.xml
- improved support for time based builds
These have been addressed in the latest code in cvs.
It would be helpful if the automatic rebuild after a failed build feature were made optional with a property in config.xml. It's not a feature to everyone, especially those with long build/test cycles. Another option would be to try the automatic rebuild once to get over any transient problems, and then wait for a checkin. --Randy Coulman
See buildAfterFailed attribute in CC 2.0.2 and later.
Two suggestions on HTMLEmailPublisher:
- The first person I showed CC to demanded that the emails be easily filterable. To ease this, slightly change the title from "<PROJECT> <LABEL> Build Successful" to "<PROJECT> Build <LABEL> Successful". This way, both good and bad builds begin with the phrase "<PROJECT> Build" and can be easily filtered.
- Allow the buildresultsurl to be optional. CruiseControl is quite useful and functional even without the JSP system. Make life easier on those of us with firewall issues and let us use just the build-loop.
Both of these suggestions are now in CC 2.0.2
I miss the StarTeam (V 5.2)Support in CC 2.0.2 
StarTeam is supported in CC 2.0.2, but you'll need to add the StarTeam jar to cruisecontrol's lib directory to build it.
I did that (StarTeam 5.2 starteam-sdk.jar) and removed the
<exclude name="**/StarTeam/"/>
from the build.xml so the StarTeam class compiles.
However, I do get Runtime Classloader Problems for the classes:
com.starbase.starteam.ServerException
com.starbase.starteam.Item
Sorry, for the Discussion here 
paul.bernet@crealogix.com
Probably want to discuss this on the cruisecontrol-users mailing list instead of here. I don't actually use StarTeam (but I do know that you shouldn't have to remove the exclude). Hopefully someone on the list will have an idea what the problem is. (Any chance you have an onld starteam-sdk.jar on the classpath?)
We are using CMSynergy instead of CVS. Is ít going to be supported by cruisecontrol?
It will be as soon as someone writes a plugin...
Someone has.
Ant like parameters for the configfile
It would be very convenient to be able to use parameters inside the config.xml file. Similar like ant with ${XX} and you may then override any setting from the console by setting -DXX=YY when you start CC.
part of CC 2.2.2
