What's new in QuickBuild 6.0 and 6.1

QuickBuild 6.0 introduces Single Sign-on, permission set to simplify the permission management, Gerrit integration, JFrog Artifactory integration, Accurev proof build, and many other improvements.

Get QuickBuild 6.1

The free license is already included

Single Sign-on integration

Now in security setting page, you can optionally specify the http header to trust user name from. QuickBuild will take value of the header as name of an authenticated user when the remote ip address is trusted (refer to trust IPs below), and user information such as email and groups can be fetched from authenticators defined above. This makes QuickBuild working in a single sign-on environment, with some third party software (such as Apache httpd server) actually authenticating the user and then forward the authenticated user name to QuickBuild via this header by means of reverse proxy.

Permission set definition

Often you might find yourself in a situation where the same set of permissions need to be assigned to different groups and configurations again and again. The permission set feature comes to rescue: it lets you select a set of permissions and give it a name, then you can assign that permission set as a whole to configurations just as other individual permissions. After the permission set has been defined, you can then assign it to corresponding configurations when define authorizations of the group.

Run as arbitrary user by administrators

Users with administrative right can now select to run as arbitrary user via user management page. This makes it easy to check profile of certain users, such as checking user permissions, or review shared dashboards, etc.

Step live log

Live log can now be monitored per step to avoid log entry interlacing if multiple steps are running concurrently. One can also check logs of finished steps to analyze possible build issues before the whole build finishes.

Gerrit integration

With Gerrit integration, QuickBuild can now build against open changes in Gerrit, and score relevant Gerrit label based on build result. Further the configuration can be scheduled to rebuild changes automatically if new patch sets have been added to changes at Gerrit side.

JFrog Artifactory integration

Artifacts can now be published to JFrog Artifactory server via the Artifactory publish step, and build information will also be created at Artifactory side to associate with these artifacts. Published artifacts can also be used by other configurations as dependencies. And these configurations can get built automatically (if scheduled) if any of these dependencies have been updated at Artifactory side.

Accurev proof build

With Accurev proof build support, one can push active changes from local Accurev workspace to QuickBuild for build verification, and can tell QuickBuild to promote these changes to upstream upon specified condition. This makes build verification of your changes in different environments a lot easier without the need to create and maintain a lot of configurations at QuickBuild side.

SCM changes aggregation

Like all other reports, now, SCM changes can be aggregated in high level configuration, so it can show recent changes summary and statistics data.

Step to record SCM changes

Often you might want to record SCM changes of particular repositories without actually checking the code out. Now this is possible with the new "record change" step in repository category.

Custom banner

With some html snippet in system setting, QuickBuild can now display customized header at top of the page to show your desired information such as company logo, site marks, etc.

Find repository/step/variable overrides and usages

Over time, you may find it is necessary to cleanup/refactor various definitions in QuickBuild, and the ability to find definition override/usage makes such task a lot easier. You will be able to get the list of child configurations where certain definitions is overriden and where they are used.

Optionally run scripts after deletion of configuration and build

Custom scripts can be defined in advanced setting of configurations to run upon configuration and build deletion. Just as other settings, they can be inherited and overriden at child configuration level.

And many many more

Click here for a full list of enhancements and bug fixes.