PMEase Build System

Here at PMEase we use QuickBuild to build QuickBuild itself. For security reasons, PMEase.QuickBuild.Release is the only configuration available for public access, and it is used to publish and manage QuickBuild public releases.

Our download page is backed by this configuration. It utilizes QuickBuild's remote API to extract the latest release information and to publish it. With QuickBuild, our development process is streamlined and greatly simplified:

1. Developer commits code in the Version Control System and gets a quick feedback about his/her checkin through the continuous integration configuration PMEase.QuickBuild.<branch>.CI (not visible for security reasons).
2. QA tests against the latest build in configuration PMEase.QuickBuild.<branch>.QA (not visible for security reasons).
3. Release manager promotes one of the proved QA builds into the release configuration PMEase.QuickBuild.<branch>.Release to publish the new release.
4. Our web site captures and displays the new release information automatically through QuickBuild's remote API.
5. Our JIRA instance captures the new release information and automatically associates it with the recently fixed issues. Click here for more information about the JIRA integration.

JA-SIG QuickBuild Instance

This instance is run by JA-SIG to build their open source projects, including the famous CAS (Central Authenticating Service) project originally created by Yale University.

Thanks Scott Battaglia for sharing!

Sandbox

A sandbox has been set up to demonstrate the features of QuickBuild. You can experiment with triggering a build, checking a code into our demo Cvs repository to trigger real time continuous integration build, with playing with remote builds, etc. A few things worth reading before you dive in:

1. Configurations under root.basic-samples are created to demonstrate basic use cases.
2. Configurations under root.remote-builds are created to demonstrate remote and parallel build use cases.
3. Configurations under root.promotion-samples are created to demonstrate build promotion use cases.
4. Configuration root.realtime-CI is created to demonstrate realtime continuous integration use cases.
5. Configuration root.JIRA-integration is created to demonstrate how to integrate QuickBuild with JIRA. Click here for more information about JIRA integration.
6. Configurations under root.VCS-samples are created to demonstrate how to configure QuickBuild for different Version Control Systems.
7. Configurations under root.builder-samples are created to demonstrate how to configure QuickBuild for different builders.
8. Configurations under root.Hibernate3 are created to demonstrate how to build a real project.
9. Configurations under root.DOTNET-sample are created to demonstrate how to build against Microsoft .NET projects.
10. You (authenticated as anonymous user) do not have the permission to edit configurations in the demo site, but you will be able to trigger builds under root.basic-samples, root.remote-builds, root.promotion-samples, root.Hibernate3, root.realtime-CI, and root.JIRA-integration.
11. Due to limited resources of the demo machine, only one build queue is configured with three working thread. Consequently, only three builds can be performed at the same time; other triggered builds will wait until there is a free working thread available.