QuickBuild 1.1 - LDAP and enhanced build promotion support

Discussions

News: QuickBuild 1.1 - LDAP and enhanced build promotion support

  1. PMEase has announced the availability of QuickBuild 1.1, a J2EE web application specifically designed to automate and manage software builds, with features such as build definition inheritance and overriding, build promotion, etc. It acts as a build platform unifying various build types, such as continuous integration builds, nightly builds, QA builds, and Release builds. This release comes with extensive LDAP support. Various LDAP servers have been tested including Microsoft Active Directory. Besides authenticating users through the LDAP server, group information in LDAP can be leveraged to set user permissions on the QuickBuild side. Also the build promotion feature has been greatly enhanced in this release to achieve flexibility. This feature is designed to move builds between different stages during software development. For example, you may promote a nightly build as QA build for deployment and testing, or promote a gold QA build as release build and tag the source code with a formal release label, etc. Custom steps can be executed during the promotion process to execute tasks such as sending notification to interested parties. Many of our customers rely heavily on this feature to streamline their development process, and have come up with a lot of comments since version 1.0. This led to a re-design of this feature. Now besides the ability to re-construct a build from source during promotion, artifacts of an existing build can be promoted into a new build and additional steps can be executed to further process them. At the same time the source code can be re-labeled with new version. A few usage scenarios at http://www.pmease.com/public/docs/guide/ch14s05.html give more detail information on how this feature works. Other new features include:
    • Send build notification to the user who triggered the current build.
    • Build against specified Subversion revision or Perforce change number.
    • Include Subversion revision or Perforce change number as part of build version.
    • Re-produce a Subversion or Perforce build even if it is not labeled.
    • Display repository change logs since last successful build.
    • Remove all password information when exporting database content to external XML file.
    • A new step type ("trigger build in another configuration") has been added so that other builds can be triggered selectively by current build.
    • A new step type ("label promotion") has been added to support label promotion at repository side. With this step, when a StarTeam build is promoted from QA to Release configuration, QuickBuild can be configured to promote the build label from QA to Release state at StarTeam side.
    • A new step type ("fail current step") has been added so that the build can be failed if a particular condition can not be satisfied.
    • Error/Warning/Debug information in the build log can be configured to display in different colors.
    • A new repository type ("Perforce (use template)") has been added to support Perforce templates.
    • Perforce repository use is enhanced to support label locking after build.
    • Monitor particular StarTeam promotion state, and trigger new build automatically if a new label is attached to that state.
    • Monitor recommended/latest baselines for ClearCase UCM model, and trigger new build automatically if these baselines are changed.
    An online demo is available at http://www.pmease.com/OnlineDemo.page. Various usage scenarios are available at http://www.pmease.com/public/docs/guide/ch14.html. Message was edited by: joeo@enigmastation.com

    Threaded Messages (5)

  2. Great Software[ Go to top ]

    Quickbuild has been well worth the purchase price. In addition to the great features it contains, the support is excellent. The usual turnaround time for the bug fix and feature requests I've submitted is usually within a few (1 - 3) days.
  3. We use Cruise Control for automated builds / deploys in our projects. Matter of fact, for some of our recent smaller projects, we have explored the use of Continuum. Continuum is so so simple to setup - takes about 5 minutes overall. The price we pay for this ease of use is that Continuum does not offer some features available in Cruise Control. But it works very well because the projects are so small. So I wonder, how does QuickBuild compare against these too? Thanks, Anoop
  4. Certainly all of these three tools can be used to run continuous integration builds. However QuickBuild puts extra emphasis on build management: 1. Build definitions are organized into a tree structure for better visualization and simply build definition for multiple projects/branches. For example, you may have the following build definition structure: -Department1 ---Project1 -----Branch1 -------CI builds -------Nightly -------QA -------Release -----Branch2 ... Common objects (such as version control system, builder, notifier) can be put on high level node, and they can be reused or overrided in low level nodes. In this way, the build definition for many projects can be greatly simplified. Also each node supports variable definitions and these variables can also be inherited and overrided in descendent nodes and be used through OGNL expression when define various properties. A typical use of variable would be define the Ant path at high node, and use this variable when define Ant builder in descendent nodes. In this way, when you want to upgrade your Ant version, you only need to change definition of that variable. 2. As already introduced in the announcement, the build promotion feature promote build from one stage to another ( in the above example, it may be promoted from nightly to QA, or from QA to Release), and each stage is only accessible to certain group of persons. In this way, QuickBuild introduces a build centric development process. 3. Build dependency handling and remote/parallel build support through a special QuickBuild repository. QuickBuild treats itself as another version control system managing build artifacts. And you can checkout artifact from another QuickBuild configuration to construct current build. 4. It is flexible through use of OGNL expressions and variables. To get a full understanding of QuickBuild's functionality, you may take a look at various usage scenarios listed at end of the announcement. Regards. Robin
  5. Based on Luntbuild[ Go to top ]

    Hi, maybe it should be noted, that quickbuild is based on luntbuild (developed by the same guys) (http://luntbuild.sf.net). Compared to continuum luntbuild is more powerful and quickbuild is a superset of luntbuild. regards, Ingo
  6. You are right, Ingo. However, QuickBuild is developed from scratch based on lessons of Luntbuild, and the code base is totally different. Regards. Robin