Luntbuild is an open source daily build tool hosted at http://www.luntsys.com/luntbuild/. It is based on apache ant, but it does not matter if you are not familiar with ant, or already have a makefile or build script with no relates to ant. There are detailed information in the document tells you how to write a very simple ant build script to wrapper your makefile or build script.
Builds automation and management are done through concepts of projects, views, schedules, modules, etc. All configurations and monitoring tasks are performed from a clean web interface. It supports scheduled builds, force builds, rebuilds, clean build, increment build, etc. Within luntbuild, you can easily combine different modules from the version control system with different branches or labels, and construct your required build, and make its status trackable, be downloadable, and etc.
Roughly, luntbuild works in the way like most other build tools does:
- Get source code from a version control system
- Set a label on current source code
- Run a ant build script in the source tree
- Publish the build log and build artifacts
luntbuild provides the following benefits:
- It is open source and free
- The configuration and monitoring is simple, all from a clean web interface
- It is not only a build scheduling system, but also a build artifacts management system. You can easily navigate for history builds.
- It has the notion of "view". By using view, you can configure multiple modules with different branches or labels, and combine them together to build.
- Flexible clean and increment build management. For example, you can schedule a nightly build and let it been clean build in order to achieve reliability. And you can schedule a hourly build and let it been increment in order to achieve speed.
- Easily manual build or rebuild of history build.
- It can populates build information into a property file from which your application can read and show information such as build number, build date, upgrade hyperlink, etc.
- Flexible versioning strategy which you can configure easily.
- Be able to use different jdk or ant for every project/every view.
- 100% pure java code, run cross-platform
Would you please provide some links how this relates to this WikiWiki. Otherwise it will probably be deleted as advertising spam in no time.
The link is indicated in top message, here is a detail:
It does relate to this Wiki as a option tool for
ContinuousIntegration.
Luntbuild-1.0 has been released. Many important features has been added, such as only perform build when there are changes in source repository, email notification about build status, only label successful builds, search and delete builds, etc. See release notes for detailed information
Luntbuild-1.1 has been released. Here are the release notes:
- Build notifications can be configured to send to users who has checked in since last build
- Build notifications can be sent to MSN messenger besides email.
- Remoting API added, so that functionalities such as triggering build, modify project/view properties, search builds, get build information can be accessed programmatically
- A composite vcs adaptor has been added to support build from mutiple repositories of same of different vcs types
- Build can be configured to run based on user defined conditions, such as repository modified, execution result of an external command, etc.
- Build success judgement can be customerized, for example, based on return code of ant command, or success/fail pattern occurred in the build log
- Reserved values of "what to build" property of UCM clearcase adaptor are now surrounded with '<' and '>', for example "<latest baselines>" will represents to build against all latest baselines, while "latest baselines" will simply represents to build against the baseline named "latest baselines".
- "next build version" property of a view are now enhanced to support more flexible versioning strategies, such as including build date, build iterations, etc.
- "is cygwin cvs" property been added for cvs adaptor to get luntbuild works with cygwin cvs correctly.
- Extra options can be set for base or UCM clearcase adaptor to control behavious such as end of line modes for checkouted text files, etc.
- "convert EOL" property been added for starteam adaptor to control end of line modes for checkouted text files.
- "line end" property been added for perforce adaptor to control end of line modes for checkouted text files.
- Fix the bug that luntbuild can not work with cvs-1.1
Visit
http://www.luntsys.com/luntbuild/ for detailed information
Lunt Build