You are viewing an old version (v. 2) of this page.
The latest version is v. 14, last edited on Mar 10, 2014
(view differences
|
)
<< View previous version | view page history | view next version >>
<< View previous version | view page history | view next version >>
Release Highlights
FEATURES AND IMPROVEMENTS
- Define global environments in composite step so that child step can inherit and override them
- In case build and step is waiting, detect and show the reasons
- Define custom columns to be displayed in build request table and build history table
- New maintenance step to remove obsolete accounts no longer existing in LDAP server
- Artifact download URL is now sensitive to the selected build type
- QuickBuild repository option "latest finished build" should not fail downstream build even if the build is failed
- Cancel triggered build upon cancelling the master build if master build is set to wait for finishing of triggered build
- Optionally wait for start of a build in order to record build id in trigger build step
- Be able trigger build as another user from RESTful API if permitted
- Remove workspaces from active nodes when delete configurations
- Transaction number field in Accurev repository is now scriptable
- Prevent any user from querying all builds in the system via RESTful API to protect the system
- Use fixed width font for edit boxes
- Move the Step action icons to reside on the left side only
FIXED BUGS
- Running a build for the first time does not auto-refresh the build overview page
- Operation of disable/enable configuration is not audited
- P4 proof build reports "can not clobber writable file" if clobber option is not checked
- P4 proof build reports "can not write readonly file" when reverting local changes in special cases
BACKWARD COMPATIBILITY ISSUES
Important
- When upgrading to QuickBuild 5.0.14, you may need reinstall QuickBuild for JIRA plugin, as the old plugin is not compatible with the new REST API supplied by QuickBuild.
Documentations |