tfs2017

TFS 2017 test task run fails on VS 2017 build machine if code coverage is enabled

落爺英雄遲暮 提交于 2019-12-05 18:20:12
We're executing a number of tests on a build machine with VS 2017 Enterprise where we've enabled code coverage on the Visual Studio test task. This fails with the following error in the TFS 2017 console: ##[section]Starting: Test Assemblies **\*test*.dll Preparing task execution handler. Executing the powershell script: d:\builds\4\_tasks\VSTest_ef087383-ee5e-42c7-9a53-ab56c98420f9\1.0.60\VSTest.ps1 C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\Extensions\TestPlatform Working folder: d:\builds\4\3\s Executing C:\Program Files (x86)\Microsoft Visual Studio\2017

Can Jenkins pull TFS gated checkin code for build?

好久不见. 提交于 2019-12-05 02:51:37
问题 I'm trying to make Jenkins pull TFS gated checkin code but failed to do so. I have managed to add a Jenkins build step in TFS, This build step is a "trigger" to start a build job in Jenkins, This job taking the source code from TFS and compile it, the problem is that this code is without the gated checkin. For example: My code base is "A" and compilation is working. I'm pushing new change (lets call it "B" delta) that should break the build (invalid c# syntax). This trigger a build in TFS

Is it possible to create a docker container from TFS and deploy a release build to it?

江枫思渺然 提交于 2019-12-05 02:46:34
We are running on-premises TFS 2017. I would like to create a release definition for our QA team which will create a Docker container running Windows 7, and deploy our release build to it automatically. Once the deployment is done the QA team should be able to log onto the container to test the app. No manual running of a MSI installer or Setup.exe. Ideally each queued release will create its own container with its own copy of the released build. Is this possible? Or recommended? All our servers and hosts will be in-house, we will not be using Azure. Thanks in advance for any advice. It is

TFS Build Agent failing to connect to HTTPS git in TFS 2017 when running as service

十年热恋 提交于 2019-12-04 20:38:39
问题 We are using an internal certificate on our server and I've followed the steps in https://blogs.msdn.microsoft.com/tfssetup/2016/12/19/error-ssl-certificate-problem-unable-to-get-local-issuer-certificate/ as well as the steps here: https://blogs.msdn.microsoft.com/phkelley/2014/01/20/adding-a-corporate-or-self-signed-certificate-authority-to-git-exes-store/ Error when running as a service: git version git config --get remote.origin.url git config gc.auto 0 git config --get-all http.https:/

TFS2017.2 NuGet restore task - ETIMEDOUT 93.184.221.200:443

☆樱花仙子☆ 提交于 2019-12-04 19:58:23
问题 I have couple of build definitions that are using the "old" NuGet Installer task to restore the dependencies from our internal TFS feed (same collection); the feed url is specified through the NuGet source parameter: The restore process is working fine as below: Switching to the newer version of the task is causing the build failure: How can I disable the connection attempt to 93.184.221.200:443 due to the fact that the build agent doesn't have internet access? I'm using TFS 15.117.26714.0.

How do I use the tfs-cli (tfx) to update a TFS extension for an on-premise TFS instance?

廉价感情. 提交于 2019-12-04 18:05:24
My company has a on-premise TFS 2017 instance. I know how to install and update extensions through the web interface, but it's pretty tedious. I'm wondering if there's a quicker way to do it with tfs-cli . Took me awhile to figure this out for some reason. At first I thought tfs-cli could only be used to publish extensions to the Visual Studio Marketplace, but that's not the case. Here's how to do it for on-prem TFS: Generate a personal access token You can follow the instructions here . Or: Hover over your profile picture in the upper right corner. Select "Security". Select the "Personal

Force removal of TFS 2017 build agent

て烟熏妆下的殇ゞ 提交于 2019-12-04 11:59:55
问题 Installed the tfs 2017 (update 1) build agent on a machine and ran config.cmd to connect it to a TFS server. That server had to be reconfigured and the original url that the build agent was pointing to is no longer valid. All I want to do is reconfigure the build agent to connect using the new url. When I run config.cmd again, it says that I must first call 'config.cmd remove' but when I run that, it fails because it is trying to reach out to the original url to remove itself from the agent

Visual Studio 2017 Cannot Move Shelveset to Another Branch

 ̄綄美尐妖づ 提交于 2019-12-04 10:06:37
问题 Since they have supposedly integrated most of the Power Tools functionality into VS2017, the new command "tf unshelve" does not work the same as the old command "tfpt unshelve" to move shelvesets to another branch, as you cannot add a source and a target using the new command. I really don't want to have to install VS2015 on my laptop just to move a shelveset. Does anyone know how to do this with VS2017? I'm having a hard time believing this is no longer possible. Any assistance is greatly

Code Coverage in .Net Core 2.0

孤街浪徒 提交于 2019-12-04 02:37:22
How can I generate code coverage in .Net Core 2.0? I tried the following: "TestPlatform\vstest.console.exe" --collect:"Code Coverage" But I got this error message: Data collector 'Code Coverage' message: Cannot find CodeCoverage.exe. I tried dotCover latest version 2017.2 which I am able to get the coverage on the local machine, but when the same is run in the TFS Build no coverage information is generated. I am not sure when NetCore Test task in TFS will get support for code coverage. How can I publish the results from DotCover in TFS also, to use DotCover Commandline to generate the Coverage

How to promote a child branch as the Trunk branch in Team Foundation Server

旧街凉风 提交于 2019-12-04 02:00:00
问题 In Team Foundation Server we have several child branches and a Trunk branch. But now we need to promote a child branch as the Trunk branch and discard the current Trunk branch. Furthermore, we need to maintain the history of both the previous Trunk branch and the child branch. PS: We cannot merge the current Trunk branch and child branch due to huge conflicts all over the project. Please go through the visual representation as well: 回答1: Even without knowing the entire context, this doesn't