List of changesets and updating work items
In the days of XAML Builds in TFS, the build would rather handily update the work item with the appropriate “Integration Build” value… The good news is, we can handle this in v Next builds using the Team Services REST API for Work Items. You can generate a special token to use for this – so you don’t need to use your actual account. You’ll need to add the following Power Shell script into your code repository, so it is available during the build. Convert]:: To Base64String($token Bytes) $headers = @ [String] $collection Address = "$env: SYSTEM_TEAMFOUNDATIONCOLLECTIONURI" [String] $project = "$env: SYSTEM_TEAMPROJECT" [String] $build Id = "$env: BUILD_BUILDID" [String] $build Number = "$env: BUILD_BUILDNUMBER" Try Catch This script will dynamically obtain the base addresses of your team collection and will get the work items related to the build, and then update the “Integration Build” value.
Along came v Next builds in TFS / Visual Studio Online / Visual Studio Team Services, which solved all of the pain of setting up and maintaining builds, but which also didn’t update the “Integration Build” value on the work items.
Now you can add a Power Shell build step to your v Next build, calling the Power Shell script and passing the VSTS Username and Password.
The next time a build triggers for a changeset that has associated work items, those work items will be updated with the build number…
Is this possible can we get a successfull status on the overall status of the build even though unit tests fail Thanks for your reply.
We do have plenty of good builds that compiled successfully, and no tests failed because we do not have any automatically run unit tests.
You're correct that you can't add a single item, but the OP seems to think that those methods don't even allow a single list to be updated (i.e.
After queueing a build job, I have a look at the current Build step.There is no simple workaround for changing the definition of a "good" build, but there are workarounds you could use to change the default behavior of the Gen Checkin Notes Update Work Items task.Which appear to export/import all the global lists as a single XML document.You can view the build report by double-clicking the build in Build Explorer. The build name is based on the build definition name, a date stamp, and a sequential number. The build name provides a link to the drop location that contains the built binaries. These entries will vary depending on the build type used and whether the build was successful.The build steps also include date and time stamp indicators such as 06/20/2006 .00).