2.1.30

Added by Robin Shen, last edited by Robin Shen on May 05, 2010
QuickBuild2 Documentation

Quick links

Changes since 2.1.30

  1. Add the ability to publish artifacts as links. This feature is useful to make external managed artifacts accessible via QuickBuild web UI.
  2. Fix the bug that dependency build running on agents might report OperationNotSupportedException.
  3. Fix the bug that StarTeam integration reports "DLL not found" even if StarTeam SDK is installed.
  4. Add copyFile/copyDir methods to "util" object in scripting API.

Changes since 2.1.28

  1. Fix the issue that triggering a dependency build as non-administrator user will result in a LazyInitializationException if dependency build is on a different QuickBuild server.

Changes since 2.1.27

  1. Fix the issue that sometimes QuickBuild reports directory not being successfully created on network share while the directory is actually created.

Changes since 2.1.26

  1. Fix class cast exception when save user agent attributes.
  2. Fix validation error when migrate from QB1.

Changes since 2.1.25

  1. Fix the issue that QuickBuild may report the error "Unconnected sockets not implemented" on some JVM.

Changes since 2.1.24

  1. Enhance Accurev repository to be able to detect changes from specified streams.
  2. Fix the issue that the same build vesion might be used if next build version is inherited from ancestor configuration.
  3. Fix the issue of not being able to authenticate via ldaps protocol.

Changes since 2.1.23

  1. Display build error messages only after build finishes to avoid the EOF exception when step log is clicked.
  2. Make the priority field scriptable.

Changes since 2.1.22

  1. Fix the issue that QuickBuild uses whole Perforce repository for checkout instead of reporting an error if the template client does not exist.

Changes since 2.1.21

  1. Fix the issue when viewing source code from checkstyle or PMD reports, the violated code fragment is not highlighted.

Changes since 2.1.20

  1. Fix the i18n issue with source view/diff.
  2. Fix the i18n issue with CPD report.
  3. Add a separate tab to explain Findbugs bug code.

Changes since 2.1.19

  1. Include sample plugins mentioned in the plugin development guide.

Changes since 2.1.18

  1. Fix the issue that cleaning node workspaces may cause a build timeout.

Changes since 2.1.17

  1. Fix the issue that sometimes a NullPointerException is thrown when access dashboard if a configuration is newly created by some other user.
  2. Fix the issue that sometimes the duplicate entry database constraint is violated for Perforce/ClearCase/Accurev builds.

Changes since 2.1.16

  1. Fix the issue that slash character in variable prompt name and description causes build and promotion option screen failing to be displayed.
  2. Make promote destination field being able to accept multi line input.
  3. Add link to Queue in scripting help popup.

Changes since 2.1.15

  1. Fix the issue that calling to "build.renderLogAsHtml()" is failed in velocity template if build is triggered by non-adminstrator.
  2. Fix the issue that tray monitor may miss build notifications.
  3. Fix the issue that exception of 'reuse-instance' will be thrown upon accessing various reports when QuickBuild server is running under IBM JDK.

Changes since 2.1.14

  1. Add scripting API getAttribute(name, defaultValue) to grid node.
  2. Enhance command build step to be able to execute a command without waiting for its finishing.

Changes since 2.1.13

  1. Fix the issue that promote and build screens may throw exception if there are some prompted variables.
  2. Fix the issue that the quote and back slash chars in variable prompt description and selection values cause build and promote option screen failed to be displayed.
  3. Improve the RESTful API to handle build cancelling.

Changes since 2.1.12

  1. Fix the issue that when original xml report contains namespace, the report will not be published correctly.
  2. Fix the issue that when failed parsing original xml report, the statistics numbers in dashboard are wrong.
  3. Add failed reason for each UnProcessed Report.
  4. Fix the issue that a bad build agent causes all builds to fail before it is timed out and removed from grid.

Changes since 2.1.11

  1. Fix the issue that web UI may respond very slowly if QuickBuild has connection problems to build agents.

Changes since 2.1.10

  1. Add VIEW_SOURCE permission to control whether or not a group can access source code in change sets.
  2. Display javac task outputs in Ant as warnings instead of errors.
  3. Fix OutOfMemory error when build generates many many lines of logs.
  4. Fix the issue that agents experiencing connection problems can not be removed from grid.
  5. Display unprocessed reports when process custom statistics report.
  6. Fix the issue that the statistics chart is empty when there is only one data
  7. Enhanced the CPD source code view (add block color to duplicated codes).
  8. Fix the issue that non-admin users can't view SCM activities although the permission of access build changes has been assigned.

Changes since 2.1.9

  1. Fix the issue the statistics chart is incorrect when begin date doesn't equal to end date in grouping by month mode.
  2. Fix the issue that statistics page will throw exception when start date is Tuesday.
  3. Enhance display of system out log for JUnit.
  4. Fix the issue that there is no build version tick in history statistics chart.
  5. Fix the issue that fully qualified host name may be used in agent causing Perforce client unable to be created.
  6. Fix the issue that NAnt build step is detected as failed even if it is actually successful.

Changes since 2.1.8

  1. Fix the bug that QuickBuild can not send notification email to Perforce committers not registered as QuickBuild users.
  2. Enhance forced notify setting to be able to send build notifications to committers since previous successful build.
  3. Support to embed scripts in selection item if variable is set to "prompt as selection box".
  4. Enhance statistics chart tooltip and metrics details table to display the build information.
  5. Fix QB-531: Comparison of statistics throws an exception.
  6. Fix the issue that statistics page may throw an exception when navigate between different configuration.
  7. Fix the issue that history statistics chart always display zero.
  8. Fix incorrect point in statistics chart.

Changes since 2.1.7

  1. Fix a security issue that user with permission to view configuration settings may get SCM passwords via RESTful API.
  2. Enhance RESTful API to get executed steps and used repositories of a build. Refer to http://wiki.pmease.com/display/QB21/Interact+with+Builds for details.
  3. Fix the issue that an exception will be thrown when opening successful/failed/cancelled/running/waiting builds page.

Changes since 2.1.6

  1. Fix the issue that user agent may not able to be timed out if it is shutdown.

Changes since 2.1.5

  1. Fix migration issue from QB 1.x
  2. Add scripting API: build.renderLogAsText() and build.renderLogAsHtml()

Changes since 2.1.4

  1. The graph options, group options, etc. in statistics tab will be remembered when changing between the different metrics.
  2. Fix the issue that Visual SourceSafe change detection may not work on Windows versions without MSVC5 runtime installed.
  3. Fix the issue that tray monitor is not visible in my page for non administrators.
  4. Fix the issue that UI may get locked if server can not connect to agents.
  5. Fix the issue that step log URLs are incorrectly rendered in build notification email.
  6. Fix the issue that FindBugs link in build summary popup is incorrectly rendered.

Changes since 2.1.3

  1. Fix the Java Service Wrapper licensing error on machines with time zone set to east of Japan (this includes Australia, New Zealand, and the pacific islands west of the date line).

Changes since 2.1.2

  1. Fix the bug that a validation error is thrown sometimes when access variables.
  2. Fix the bug that hovering mouse over "more..." link on the dashboard may leads to Hibernate LazyLoadException.
  3. Fix the bug that NullPointerException is thrown when migrate configurations with disabled promotion setting.
  4. Fix ClearCase migration issue.
  5. Fixed the bug that JUnit report publishing is failed when failure message or error message contains XML CDATA section.
  6. Fix the bug that Perforce repository does not recognize "move/rename" operation.
  7. Add back the ability of customizing view name when define ClearCase repository.
  8. Add back the ability of customizing client name when define Perforce repository.
  9. Add back the ability of customizing reference tree name when define Accurev repository.

Changes since 2.1.1

  1. Fix the bug that StackOverflowError is thrown when storage path contains scripts.
  2. Fix the bug that build error message is not included in failed build notification email.

Changes since 2.1.0

  1. Fix the bug that NPE will be thrown if triggering a build with prompted variables is cancelled.
  2. Fix the bug that variable prompting for time requires HH:mm:ss instead of HH:mm.

Changes since 2.0.x

  1. A cross-platform Tray Monitor to view build, trigger build and report build events from desktop.
  2. The custom statistics feature is added to generate user defined statistics based on arbitrary xml files.
  3. Analyze .NET NCover report to publish code coverage result and statistics over time.
  4. Analyze .NET Fxcop report to publish code analysis result and statistics over time.
  5. Analyze CPD report to publish code duplicate result and statistics over time.
  6. User can now add new SCM systems, steps, reports, statistics, notifiers and authentication systems to QuickBuild by writing custom plugins.
  7. External system can operate QuickBuild programmatically via the new RESTful API.
  8. Database backup and restore is now much faster. An option to exclude builds when backup database is also added.
  9. Support to use Oracle as external database.
  10. SSL support for QuickBuild server and agents.
  11. Improved ClearCase support. Existing dynamic or snapshot view can now be used for build, besides the ability to create new view based on config spec or stream/baseline information.
  12. Task and compilation error in Ant build step can now be catched and reported in build overview screen.
  13. Add browser back button support when navigating QuickBuild pages.
  14. Build tabs, statistics tabs, report set and report filters are now remembered when switching between different build and configuration for better navigation experience.
  15. Add an option to always display default value of the variable when it is prompted.
  16. Add scripting API to acquire and release resources when step executes. This addresses the issue of resource contention when multiple steps running on the same node with limited resources. Refer to the Resource Locking samples on how to use this API.
  17. Fix the issue that QuickBuild page sometimes throws exception if opened/viewed in multiple browser tabs.
  18. Fix the issue that sometimes variable can be specified with empty value even if it is not allowed to empty.

Major improvements over 1.x

  1. Native support for a number of build reports. Refer to below documents for details of build reports:
  2. Build statistics. Refer to below documents for details of build statistics:
  3. Build grid support. Refer to below documents for details of build grid:
  4. Introduce the concept of proof build to build/test user's uncommited changes at server, and optionally checkin that those changes automatically if build/test succeeds.
  5. Visually arrange steps to design build process. Refer to below documents for details:
  6. Build promotion visualization. Source build and destination build will be linked to show the promotion relation.
  7. Fine grained access control when assign permissions for groups.
  8. Be able to customize build option screen and promote option screen when manually triggers a build or promote a build. This is supported through prompt settings of variables.
  9. Builds can run concurrently even for a single configuration to better utilize build grid resource. To configure concurrent running builds for a single configuration, the master step needs to be configured to run on agent instead of server.
  10. Be able to recommend build. Recommended build will have a star icon attached. Promote operation can be configured to only applicable for recommended builds.
  11. Build changes will be collected during a build promotion process. For example, if a release build is generated as result of promoting from a QA build, the change set between current release and last release will be collected automatically.
  12. Be able to view/diff changed source files in the change set panel.
  13. Be able to compare two builds (not necessary ajacent) and generate changes between them.

Features exist in 1.x but not yet implemented in 2.1

  1. Eclipse and Visual Studio plugin to monitor QuickBuild.
  2. Integration with JIRA.

These features will be implemented in next major release.

Labels:

Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.