This is useful when sending backup for diagnostics. Add option to clear passwords when backup database.Add the option of auto-detecting user time zone from browser to display local date/time.A build variables tab to display value of all used variables in a build.This feature is typically used to transform issue keys into issue links for issue trackers currently not supported by QuickBuild. A general commit message transformer to transform arbitrary snippet of SCM commit message freely.A configuration specific dashboard to display brief information of a configuration, including description, next build version, overall build success rate, average build duration, error messages, recent builds, and pending build requests.Step success rate and duration statistics.For example, you may define promote actions such as deploy to dev server, deploy to QA server, release, and they will appear on build page conditionally based on status of the build and permission of current user. Multiple promote actions can be defined, with the ability to define condition of each action.Drag and drop steps to rearrange build workflow.This makes examination and modification of inherited settings much easier. Inherited settings such as steps, repositories and variables will be displayed directly in descendant configurations.A non-admin account can now be authorized to administer a configuration subtree.Support to analyze and publish MSTest report.Bugs can be searched by summary within QuickBuild. A Bugzilla bugs tab to display information of bugs relating to current build, or comparison of two arbitrary builds.Transform Bugzill bug numbers in SCM commit messages to bug links.Tickets can be searched by summary within QuickBuild. A Trac tickets tab to display information of tickets relating to current build, or comparison of two arbitrary builds.Next build version in QuickBuild can be configured to use next unreleased Trac milestone.Tickets fixed in a build can be associated with corresponding Trac milestones automatically via milestone field of the ticket.Further, build version can be pushed into Trac as released milestone if it does not exist already. Milestones in Trac can be automatically released if certain build is successful.For example, you may configure QuickBuild to create a ticket for build failure and have it assigned to build engineer, or create tickets for unit test failures and have them assigned to corresponding developers. Create Trac tickets under certain conditions and assign to certain person.Tickets will be updatede under the Trac account associated with the SCM committer. For example, fix #123 -comment some comment tells QuickBuild to fix ticket #123 with a comment some comment.
#QUICKBUILD MSTEST UPDATE#
Update Trac tickets based on commands found in SCM commit messages.Transform Trac ticket numbers in SCM commit messages to ticket links.User may view/diff changed files of issues directly from JIRA without FishEye being installed. A QuickBuild plugin running at JIRA side to disclose SCM changes and builds information for an issue.Issues can be searched by summary within QuickBuild.
Major Improvements over 2.1 Third party integrations
#QUICKBUILD MSTEST UPGRADE#
Check the upgrade guide for incompatibilities with 2.x.
0 kommentar(er)
