New

What's new in QuickBuild 5.1

  • Verify GitHub pull requests and update pull request status based on build result
  • GitHub issue tracker integration to parse issues in commit messages
  • Leverage perforce shelve/unshelve feature to run pre-commit builds without using user agent
  • Retrieve changes of Subversion externals for source view and diff
  • Custom columns to display custom build and request info
  • Display reasons for waiting builds and steps
  • Define environment variables in composite steps for inheritance and overriding
  • Detect broken communication links to agents to fail build fast
  • Drag&drop to organize favorite dashboards
  • Dashboard list to display all dasbhoards in system
  • Resource access information to know about resource usage status
  • Coverity report rendering

Github integration to verify pull requests and update pull request status based on build result

A configuration can be setup to monitor open/closed pull requests via the newly added GitHub repository type. When new pull request is created or existing pull request has received new commits, a separate build corresponding to the pull request will be fired to do the verification. Pull request status at GitHub side will be updated with the build result.

A branch property is added to build to tell apart different builds associated with different pull requests in the same configuration. And changes of certain build will be calculated against previous build with same pull request.

GitHub issue tracker integration to parse issues in commit messages

The integration with GitHub issue tracker features:

  • Issues mentioned in the commit messages can be hyper-linked
  • A nice issues report generated automatically based on all commit messages
  • For each issue, related changed files can be displayed

Leverage perforce shelve/unshelve feature to run pre-commit builds without using user agent

The proof build mechanism serves the purpose of verifying unsubmitted changes, but it requires developers to install user agent on their development machine. Also it requires that the user agent is online when proof build is finished, which is not ideal as it is impossible for developer to submit proof build and then shutdown computer to go home. The perforce shelve support in QuickBuild 5.1 comes to rescue. It serves the same purpose of verifying unsubmitted changes, without aforementioned limitations. What it does is to merge shelved changes with latest version in defined repository, run build, and optionally submit shelved changes if build is successful.

Retrieve changes of Subversion externals for source view and diff

When checkout a Subversion repository with externals, QuickBuild not only retrieves changes made in that repository, but also changes made in associated externals recursively. User can view/diff changed files of externals just like normal change sets, or even can compare changed external files across different builds.

Custom columns to display custom build and request info

Custom build info can be displayed in build summary and build history table by defining custom fields in advanced setting of the configuration. For instance, one can define custom fields to display SCM revision of certain repository like below.

Display reasons for waiting builds and steps

Sometimes it is difficult to find out why a build or step is being put into waiting state, especially when the node match condition comes complex. QuickBuild 5.1 inspects every aspect to determine the exact reason for waiting state, so that you can take action early.

Define environment variables in composite steps for inheritance and overriding

Environment variables can now be defined in advanced settings of composite steps. This makes it possible to define a set of environments in parent step to be used by all build steps underneath it. Further, child steps can selectively override environment variables defined in parent step if necessary. This mechanism makes it a lot easier to maintain different environment variables across different build steps.

Detect broken communication links to agents to fail build fast

When a build is launched, QuickBuild server dispatches steps to agents and then sits there passively waiting for agents to report step status to save server resource. This mechanism has a drawback that when agent is down or communication link to agent is broken, the build will wait there infinitely until it is cancelled or timed out. QuickBuild 5.1 cures this situation by probing agents every five minutes and cancel the build if there are any probing errors to make it fail fast.

Drag&drop to organize favorite dashboards

Everyone can create and share dashboards in QuickBuild. While this is convenient, members of big team may find it difficult to pick up desired dashboards from the large list of shared dashboards. Now with 5.1, when the list of dashboards exceeds ten, you will be able to organize your favorite dashboards by dragging dashboards between the favorite and available list. Newly shared dashboards from other users will be put into available list initially.

Dashboard list to display all dashboards in system

Administrators can now review list of all dashboards in system to know to which groups or individuals they are shared, and can edit them to modify the share list. This also provides a place for administrators to cleanup obsolete shared dashboards.

Resource access information to know about resource usage status

Resource plays an important role in QuickBuild to ensure safe access to limited availabilities of real-world resources. As more and more resources are defined, it becomes necessary to clean up obsolete or no longer used resources. The resource access information tells when and how long the resource is recently used, by which configuration. This piece of information together with the already existing resource usage heatmap provides a reliable way for administrators to determine status of the resource.

Coverity report rendering

Coverity is an important tool to find defects and security vulnerabilities in source code. Now, QuickBuild can publish the Coverity report, so you can view those defects/issues directly in QuickBuild, and futhur more, QuickBuild can track the issues trends across the builds.

And many many more

Click here for a full list of enhancements and bug fixes

Information

Message