2.0 beta9

QuickBuild2 Documentation

Quick links

Changes since 2.0 beta8

  • Replace gridgain with QuickBuild's own grid implementation for simplicity and reliability reason.
  • New load balance algorithm to distributes build loads to agents more evenly.
  • Introduce build mode concept to configuration. Three build modes are supported, respectively concurrent, sequential and disabled.
  • Absolute path support for step "Fix Line End" and "Change Permission".
  • Label lock support for Perforce repository.
  • Change queue implementation to avoid possible deadlock of dependency builds.

Changes since 2.0 beta7

  1. Tune various network operation timeouts to fit into heavy load environment.
  2. Add step pre-execution script and post-execution script.
  3. Step status graph now displays steps correctly for past builds even if they are removed from configuration.
  4. Trigger build step is enhanced to respect the trigger chain to be able to works better with configuration dependencies.
  5. Fix the issue that JVM may got restarted on heavy load.
  6. Fix the issue that empty parall composition step can not be executed.
  7. Fix the bug that junit publish step does not correctly displays muti-line error messages.
  8. Fix the bug that junit publish step does not work with the test case that crashes the JVM.
  9. Fix the bug that build log scrolls incorrectly when build is running.

Changes since 2.0 beta6

  1. Fix the critical bug that child steps defined in a sequential step always take the alphabet order.
  2. Fix the bug that IE7 reports javascript error.
  3. Fix the bug that "workspace cleanup condition" is not preserved when change step type.
  4. Fix the bug that embedded html reports are not scrollable if it is too long.

Changes since 2.0 beta5

  1. Gracefully stop QuickBuild server through menu "Administration/Server Stop".
  2. Display html report directly at right side of the build tabs, instead of poping up a new window.
  3. Add "build modify script" property in configuration to allow modification to the generated build object before actually running the build.
  4. Be able to stop running of configuration (besides the ability to cancel a build).
  5. Add back the "expand all" button to dashboard, but only available when the associated group has "expand all" permission.
  6. Be able to specify include and exclude patterns when detect changes from SCM.
  7. Change unit of build timeout from minutes to seconds.
  8. Display changed files in alphabet order.
  9. Display available/selected steps in alphabet order when define composite steps.
  10. Display child steps of parallel step in alphabet order in the step graph.
  11. Display at most 25 changes in build overview screen.
  12. Pagination support for changes display.
  13. Upgrade MVEL script engine to 2.0.13 to avoid known MVEL bugs.
  14. Add remote API method: getConfigurationPath, getConfigurationChildren, getConfigurationDescendents, and deleteConfiguration.
  15. Keep as much information as possible when change a step type.
  16. Fix the bug that a null character in log message prevents logs from being displayed correctly under internet explorer.
  17. Fix the bug that build timeout sometimes does not work.
  18. Fix the bug that build cancellation sometimes does not work.
  19. Fix the bug that proof build does not work for Subversion 1.6.
  20. Fix the bug that detected Perforce changes may not be accurate for complex client view mappings.
  21. Fix the bug that Maven builds does not use versioned defined in POM.
  22. Fix the bug that SCM changes may not be accurate if multiple checkout steps are executed concurrently.
  23. Fix the bug that migrate/import to MySQL causes QuickBuild complaining about constraint violated.

Changes since 2.0 beta4

  1. Add the "Change Permission" step to change permissions of specified set of files.
  2. Resolve the issue that the build grid does not work if JVMs from different vendors are used at the same time.
  3. Fix the bug that if build across multiple agents, a Grid exception will be thrown complaining about unmarshalling errors.
  4. Fix the bug that QuickBuild is unable to delete a temp file when transferring artifacts from agents to server.
  5. Fix the bug that NPE will be thrown if switching to a configuration without builds while viewing build reports.
  6. Fix the bug that build notification email may contain duplicated report summaries if build is configured with parallel steps.
  7. Fix the bug that if a scheduled build includes a step to trigger another build, the second build will display the "triggered by" property as "unknown", instead of "scheduler".
  8. Fix the bug that checkouting against Accurev causes QuickBuild to complain about "not serializable" error.

Changes since 2.0 beta3

  1. Be able to look up email from Perforce server, and use it to send build notifications if the committer is not a QuickBuild user.
  2. Be able to look up email from StarTeam server, and use it to send build notifications if the committer is not a QuickBuild user.
  3. Be able to look up email from LDAP server, and use it to send build notifications if the committer is not a QuickBuild user.
  4. Keeps user attribute tab selected while switch between build agents.
  5. Fix the issue that auto-refresh eats lot of server CPU cycles when there is large number of configurations expanded in dashboard.
  6. Fix the bug that non-admin user can not access build statistics and changes statistics.
  7. Fix the bug that migrating the command builder defined in 1.x will cause a "ConversionException" if the builder has property "dir to run command" specified.
  8. Fix the issue that migration script runs out of memory on 64bit JVM.
  9. Fix the bug that LDAP authenticator can not process group DNs containing slashes.
  10. Fix the bug that the web interface occasionally throws a valiation exception when deleting child configurations.

Changes since 2.0 beta2

  1. Performance improvements. Dashboard is now much faster than previous versions even there are a
    large number of configurations.
  2. The expand all button is removed from dashboard and all configuration trees since server will be very busy serving this request in case of many configurations, and improper use of this functionality can easily causes the server too overloaded.
  3. Various edit actions in the dashboard are removed and they can only be accessed when a particular configuration is selected.
  4. A children tab is added to configuration page to display all child configurations.
  5. Build step is able to run on the user agent of build initiator.
  6. Variable name is now constrainted. It can only starts with underscore characters or letters, and it can only consist of word characters and underscores.
  7. When access a variable with empty value, an empty string will be returned instead of null.
  8. If a variable is set to prompt and if an empty value is specified at prompt time, the default value of the variable will be used.
  9. Global workspace directory is removed, and workspaces on server will be created under the server installation directory just like on agents.
  10. Add Always and Never condition for build subscriptions.
  11. Published artifacts are now sorted.
  12. Fix the bug that changes can not be retrieved if ClearCase repository is configured to checkout on agents.
  13. Fix the bug that Accurev integration does not work if the build stream is backed by passthrough streams.
  14. Fix the bug that RSS feeds does not work.
  15. Fix the bug that moving builds between different configurations may cause the dashboard displaying incorrect latest builds.
  16. Various build step can now takes absolute path for build scripts.

Changes since 2.0 beta1

  1. Fix the bug of not able to stop QuickBuild server/agent on Solaris platform.
  2. Fix a bug that database is queried frequently when user interface is auto-refreshed.
  3. Simplified build agent set up: Build agents can now only be downloaded by administrator and agents installed with this package can now connect to QuickBuild server directly without authorization.
  4. DHCP can be used with build agents. Under the hood, QuickBuild uses security token to authenticate build agents instead of using static ip addresses.
  5. Configuration workspaces are named by configuration name and organized in a hierarchical structure by default.
  6. Child configurations can be easily selected by hoving mouse over the arrow next to the configuration name in the navigation area.
  7. Subversion repository is enhanced to be able to checkout urls non-recursively.
  8. Add report set support for publishing reports.
  9. Fix a bug that search results always return empty in 'By Packages' tab.
  10. Fix a bug that NPE is thrown when there is no data for JFreeChart.

Major improvements over QuickBuild 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 QuickBuild 1.x but not yet implemented in this beta

  1. Various IDE plugins inlcuding Eclipse, IntelliJ and Visual Studio.
  2. The windows tray monitor.
  3. Integration with JIRA.
  4. Remoting API.

These features will be implemented in QuickBuild 2.1


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