Luntbuild has the following features:
1. Supporting many version control systems:
   1) cvs
   2) visual sourcesafe
   3) subversion
   4) starteam
   5) perforce
   6) base clearcase
   7) clearcase UCM
2. By using the notion of project, view and module, luntbuild can be
   used to easily build multiple customerized version of products, or
   different development branches, etc.
3. Can do manual builds, or force builds
4. History builds generated with proper label strategy can be rebuild 
   later
5. Clean or increment type build can be set when scheduling build or
   do manual build. 
6. Build strategy can be set when scheduling build. For a particular 
   schedule, user can select to always build, never build, build only
   when there are changes in repository, or always build if failed. 
7. Label strategy can be set when scheduling build or do manual build. 
   User can select to always label build, or never label build, or only
   label successful build. 
8. Mail strategy can be set when scheduling build, or do manual build, 
   or do rebuild. User can select to always send notification mail, or 
   never send notification mail, or only send notification mail when 
   buid fails.
9. Build artifacts are listed as part of detail information of a build. 
   By this way, the whole team can have a centralized place to manage
   builds for downloading, testing, etc.
10. Build can be searched and deleted.
11. Build process, and scheduler status can be monitored. 
12. Build log, revision log and system log4j log can be directly accessed
    through web interface.
13. Different jdk, jdk options, ant, and ant options can be configured for
    different project/views. 
14. Different environment file can be loaded for different project/views.
15. Schedule can be periodically like, or cron like. 
16. Can create schedules using "manual" trigger type. These build schedules can only be 
   triggered manually, and can be seen as build categories. Builds can be moved between 
   different build categories to support build promotion.
17. Build artifacts can be deleted. Also new files can be uploaded to a particular build
   to support patching for builds. 