The Java Integrated Build Environment is strongly focussed on the concept of Continuous Integration. Building as when needed lets you discover bugs faster en integrate your software more seamless. The more activity the source control system shows, the more often the build system runs its actions.
The Java Integrated Build Environment runs unit tests automatically. Tests reports are generated and put in a userfriendly web interface. This facilitates the fixing of bugs, and the speed of looking up test failures.
Using the Java Integrated Build Environment, (Enterprise JavaBean) Components are automatically build, assembled, deployed and tested on as many application servers as you want. Currently, JBoss, WebLogic and WebSphere are supported, more will follow in the future.
The Java Integrated Build Environment (using CruiseControl) can automatically notify each and every developer if a build has failed for whatever reason. It can also be configured to only send mails to the people that have committed in the last build cycle.
The developers won't have to worry about how the build is configured, how components are assembled, how everything is put together. This is all done by a couple of configuration files and the developer only has to fill in his dependencies on other modules. Nothing can go wrong.
Through the use of a couple of sequence lists, the buildmeister can fully configure the sequence of the automated build, as well as the frequency of building. Also, he can easily configure what components should be assembled into a web archive, what components are enterprise javabeans, what components should be left out of the release, etc.