triadamagical.blogg.se - Teamcity release notes

#TEAMCITY RELEASE NOTES HOW TO#

The regular expression to use when matching primary workitems (stories and defects) with change comments.ĭetermines how the integration looks for Build Projects in VersionOne. The system name of an attribute to search when matching primary workitems (stories and defects) with change comments. Configure the integration setting based on the following table.Locate the "VersionOne Integration Settings" and click on the "Edit settings" link.Click the "Edit server configuration" link.Open a browser and navigate to your TeamCity URL.Restart the TeamCity application server for the changes to take effect.Rename the file to TeamCityNotificator.zip.You can determine the Team City Data directory by viewing the Server Configuration page. On your TeamCity server, copy the downloaded package into the "plugins" subdirectory located in your TeamCity Data directory.

#TEAMCITY RELEASE NOTES HOW TO#

This section describes how to configure TeamCity for use with VersionOne Using the "Build Projects" dropdown add the appropriate Build Project.Click Edit on the row for the project you want associated with a Build Project.Navigate to the Admin | Projects | Projects page.Reference - this is how the Build Project is known to TeamCity.Name - this is how the Build Project will be known to VersionOne users.Navigate to the Admin | Projects | Build Project page.Check the "Enable Build Integration" checkbox and click the Apply button.Navigate to the Admin | Configuration | System page.Log into the VersionOne application as admin.Instructions for doing this are available on the VersionOne Community Site. If you are using Team Edition, you need to manually create the Build Project.

You should see an entry in the grid for the build you forced. Select the "Build Run Quicklist" Report.Navigate to the Reports | Reports Overview page.Select VersionOne project in 'My Projects' dropdown.Force a build on the project you configured.Once configuration is complete use the following steps to verify that the build integration is working This can be a temporary location since we will copy some of these files during TeamCity configuration. Verify that you can connect to your VersionOne instance from the machine hosting TeamCityĭownload the TeamCity integration using the link above and extract it into a folder of your choice. These instructions presume that TeamCity is already installed, configured, and working properly. The latest version of the VersionOne Integration for TeamCity is available in the VersionOne App Catalog. If you are using TeamCity 4.5 you need release 4.5.4 or better. The following sequence diagram illustrates the VersionOne TeamCity Notifier behavior. When work for a story or defect was included?.

Which build contained the completed story?.

Which builds contain work for the story?.

Which builds contain work for the defect?.

Which build contained the fix for the defect?.

Which build the defect was reported against?.

Using this integration you can better address the following situations: If the build comment contains VersionOne Story or Defect Identifiers, the Notifier will create or reuse a VersionOne change-set and relate the build with the appropriate Story or Defect. Every time a build executes the Notifier creates a BuildRun asset in VersionOne with details of the build. Once the TeamCity Notifier has been installed, team members include a VersionOne identifier, such as "S-01454" or "TK-01234", in the comments of their SCM commit. This visibility is useful when identifying problem builds or generating release notes. The VersionOne TeamCity Notifier creates a record of TeamCity builds in VersionOne, so the development teams can associate stories and defects to a particular build. VersionOne Integration for TeamCity Introduction Contents