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#
Issues can be searched by summary within QuickBuild. A JIRA issues tab to display information of issues relating to current build, or comparison of two arbitrary builds.
Next build version in QuickBuild can be configured to use next unreleased version of corresponding JIRA project.Issues fixed in a build can be associated with corresponding JIRA versions automatically via fix version/s field of the issue.Further, build version can be pushed into JIRA as released project version if it does not exist already. Corresponding project versions in JIRA can be automatically released if certain build is successful.For example, you may configure QuickBuild to create an issue for build failure and have it assigned to build engineer, or create issues for unit test failures and have them assigned to corresponding developers. Create JIRA issues under certain conditions and assign to certain persons.Issues will be updatede under the JIRA account associated with the SCM committer. For example, fix TST-123 -time 2d -comment some comment tells QuickBuild to resolve issue TST-123 with a worklog of two days and a comment some comment. Update JIRA issues based on commands found in SCM commit messages.Transform JIRA issue keys in SCM commit messages to issue links.Integrating QuickBuild with JIRA and Integrating JIRA with QuickBuild.Major Improvements over 2.1 Third party integrations
#QUICKBUILD MSTEST UPGRADE#
If you are tasked with solving search relevance problems even if not in Solr or Elasticsearch it should be your first reference.Check the upgrade guide for incompatibilities with 2.x. Easily one of the most interesting technical books I have read in a long time. Relevant Search: With Applications for Solr and Elasticsearchįor more in depth reading about search, ranking and generally everything you could ever want to know about how lucene, elasticsearch or solr work under the hood I highly suggest this book.
0 kommentar(er)
