Luntbuild is designed to be installed quickly, such that a build portal can be set up for a team to enable continuous integration tasks. Since continuous integration tends to yield a lot of builds (see "Daily builds with Luntbuild"), the labeling feature can be very important.
Key features in release 1.2 are:
- Supported build tools: Ant, Maven, Shell script
- Supported version control systems: Visual Sourcesafe, Clearcase(base and UCM), file system, CVS, Accurev, StarTeam, Perforce, Subversion
- Role-based security mechanism available to let you define project admins/builders/viewers for each project
- Be able to define dependencies between different projects
- Builds can be categorized, searched, and re-produced
- Builds can be promoted - For example, a build might be noted as going from "test" phase to "release" phase
- Flexible build versioning strategy can be defined
- Notifications can be sent via e-mail, MSN messenger, or Jabber
- Remoting API available to integrate your existing system with Luntbuild
- Export/import data through XML file
Luntbuild's installation as a standalone web application seems to imply certain capabilities on the part of the container, because it doesn't require the deployer to set up a database reference.
What do you think about the product as a whole? Do you use continuous integration now? Why or why not? Does its license - more permissive than most other open source licenses - affect your opinion of the project?