XpdWiki
| FrontPage |
| RecentChanges |
| XtC |
| FindPage |
| PageIndex |
| XpApprentices |
Set your name in
UserPreferences
UserPreferences
Referenced by
ContinuousIntegra...
JSPWiki v2.0.52
LuntBuild |
|
| Your trail: | |
Difference between version 4 and version 3:
| Lines 6-10 were replaced by lines 6-7 |
| - * Supporting version control systems: cvs, visual sourcesafe, subversion |
| - starteam, perforce, base clearcase, clearcase UCM |
| - * 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. |
| + * Supporting version control systems: cvs, visual sourcesafe, subversion, starteam, perforce, base clearcase, clearcase UCM |
| + * 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. |
| Lines 12-29 were replaced by lines 9-14 |
| - HIOLA |
| - * History builds generated with proper label strategy can be rebuild |
| - later |
| - * Clean or increment type build can be set when scheduling build or |
| - do manual build. |
| - * 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. |
| - * 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. |
| - * 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. |
| - * 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. |
| + * History builds generated with proper label strategy can be rebuild later |
| + * Clean or increment type build can be set when scheduling build or do manual build. |
| + * 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. |
| + * 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. |
| + * 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. |
| + * 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. |
| Lines 31-34 were replaced by lines 16-17 |
| - * Build log, revision log and system log4j log can be directly accessed |
| - through web interface. |
| - * Different jdk, jdk options, ant, and ant options can be configured for |
| - different project/views. |
| + * Build log, revision log and system log4j log can be directly accessed through web interface. |
| + * Different jdk, jdk options, ant, and ant options can be configured for different project/views. |
| At line 38 added 18 lines. |
| + |
| + ---- |
| + |
| + Luntbuild 1.2 beta2 released with the following features: |
| + |
| + * 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 of your project. |
| + * Be able to define dependencies between different projects. |
| + * Builds can be categorized, searched, and re-produced. |
| + * Builds can be promoted, for example from "test" phase to "release" phase. |
| + * Taking the power of OGNL expression, very flexible build versioning strategy can be defined. |
| + * Be able to send out build notification through Email, MSN messenger, or Jabber. |
| + * Remoting API available to integrate your existing system with Luntbuild. |
| + * Be able to export/import data through XML file. |
| + |
| + For more information, please access [http://www.luntsys.com/luntbuild/] |
| + |
Back to LuntBuild, or to the Page History.