I'm working in a project and I'm trying to optimize testing process so, when I execute a test case and I found a bug, I would like to associate this bug to the current build.
The builds are created automatically but when I try to select the built in the droplist there are not builds to select, so... How can I do it to get all the builds that I've made automatically?
Maybe is there any issue with Global List?
Im using VS 2010 and I have installed TFS 2010 Power Tools.
Thanks in advance!!
The global list is normally updated by an event subscription on the server that handles the BuildCompleted event. On your TFS server, there should be an executable named BisSubscribe.exe. You can use that to verify or fix the subscription. For more details, check out Jason Prickett's blog post on How to filter the Build Completion Event.
Related
We have an on-premises TFS instance in our company, and we notice that the sonarqube extension is getting updated automatically. https://github.com/SonarSource/sonar-scanner-vsts
We are worried to have it updated automatically in our production environments, is it really the way it was designed to work? Is there a way to do the updates manually instead or a continuous delivery model?
Yes, this is an expected behavior. In TFS 2017 we added a feature to automatically check for updated external extensions once a day and upgrade them. No way to stop this unless you use a prior version of TFS.
If the account running the TFS Services does not have access to the internet then the jobs will just be marked as failed. They will still attempt to update everyday. To update, you then just have to download the VSIX from the Marketplace and upload it to your local gallery to update the extensions
I'm trying to associate a test run to a release if possible, and if not then a build.
I need to either be able to associate it before the run, or after when we view the history.
I've been looking online and all I can find are references to functionality of 2017 that isn't in 2015.
Is this possible?
It's not possible in TFS2015 for now. You have to upgrade your TFS server to TFS2017updae2. Detail steps please follow this tutorial: Run automated tests from test plans in the Test hub
We are using TFS2017 Update 2, but also there it is, alas, not possible to manually run test cases against a RELEASE.
It is only possible to select a BUILD, which is not accurate in our case, because our RELEASE consists of 5 different SW components, each having it's own BUILD number.
I posted this as a feature request on the user voice forum, here:
https://visualstudio.uservoice.com/forums/330519-visual-studio-team-services/suggestions/20579638-add-option-to-assign-a-release-version-to-a-test-r
Please vote.
I'm converting our XAML build process to vNEXT build for our on-premise TFS 2017. One step I like to automate is the create a work item task for a specific user to execute after the release has been done. Is there a built in way to do this? I have a PowerShell script but I'd prefer not to use it if there is already a better way
No, there is still no out-of-the-box feature for this. Either using the REST api or the Client Object model in a powershell script just like you have done will do the trick.
You could also take a look at this similar question: How to have TFS automatically add certain tasks to new work items?, jessehouwing has provided a great answer.
Another way is using TFS Aggregator- a serverside pugin for TFS 2013
(update 2 and later) which has the ability to create new work items
based on rules. An example task can be found here:
https://github.com/tfsaggregator/tfsaggregator/wiki/Auto-Create-Children
Update
After go through the extension in VSTS marketplace (https://marketplace.visualstudio.com/) , there is also no existing task could do this. You may still use your powershell script or write your own extension.
I'm using TFS 2015 on-prem and I'm using the standard SCRUM template. I have 1 Team Project and I'm using the team field to segregate work. I have created a few build definitions and ran a few builds over the last few weeks.
When I installed TFS I did not install or configure Reporting Services straight away as I had planned to do that later. I have since done this and I now have my Tfs_Warehouse which is updating with most things but NOT FactBuildProject or FactBuildDetails. Some of my other facts are pulling over, such as FactCurrentWorkItem and even FactBuildCoverage. I have rebuilt the warehouse in the TFS Admin Console.
As this is a standard process template and standard reports I expect that the required fields should be set to reportable.
How can I get data in my FactBuildProject table and where can I look for issues with it? I'm not sure where to start and I can't find anyone else in the world with a similar problem.
If you are using the new task-based build system, then you are out of luck, since that data is not being propagated to the data warehouse.
Check the comments on this blogpost: http://nakedalm.com/create-a-build-vnext-build-definition-on-vso/
I'm using TFS 2008 and the TFS Build Service. I am able to perform builds, but I'm annoyed about receiving alerts for successful builds. I only want to receive a notification when a build does NOT succeed. Not sure why I can't find this setting, but maybe it is not offered. Does anybody know if this is possible or am I missing something?
The easiest way to configure this is to install the TFS Power Tools on your machine. This will add a more powerful alerts editor into Visual Studio. You can then edit the email alert that will already exist for you, or create another one, but filter it so that you will only get notified when the build status is failed.
Jason Prickett has a blog post on How to Filter the Build Completion Event that you should find helpful. His article targeted TFS 2005, but it should be equally applicable to TFS 2008. It's a more involved process than it ought to be, but it is possible.