tfs2015

An error occurred while sending the request in TFS2015 update2 vNext build configuration

只愿长相守 提交于 2019-12-06 07:36:27
问题 While configuring a TFS vNext build agent i am getting the error: ErrorConnectingToTheServer An error occurred while sending the request. the request. I could not find any other error message in the event log or anywhere else. Please help. Update1: The SSL (https///tfs) did not work.but the plain http:// worked. Update 2: I have removed the old agents and trying to configure new one. While doing that i am getting the below error that is present in the _diag folder: System.Net.WebException:

Table WorkItemsLatest (TFS 2010) missing in TFS 2015 (Collection Database)

纵然是瞬间 提交于 2019-12-06 07:02:35
We recently migrated from TFS 2010 to TFS 2015 and came across that some of the reporting services are not working anymore. One of the view we created was pulling various information (WorkItem State, Title,Fld10118) from "WorkItemsLatest" table, however, checking the collection database of TFS 2015 indicates that there is no more "WorkItemsLatest" table in TFS 2015 collection database. I would appreciate if you can advise how to get above mentioned fields in TFS 2015 collection database. I understand that the operational databases are not supported by Microsoft and encourages to retrieve data

TFS Build 2015 not publishing test results

允我心安 提交于 2019-12-06 04:49:55
UPDATE (I have restructured this question with a new and basic solution and build as the same problem exists there) I'm using the new build system in Tfs 2015 and I'm using Update 1. I have noticed that on the build summary screen, no test results or Code Coverage results are submitted: I have a test step which runs and contains results and I have a .trx and a .coverage file but the test step log contains the warning: ##[warning]Failed to publish test results: The value for the Build.Id property is not within the permissible values for it. The Build is very basic, it contains 2 steps and Code

The session for this agent already exists

人走茶凉 提交于 2019-12-05 23:51:57
问题 I am using TFS to execute a nightly build that includes several steps that use the TFS Test Agent. I am running the latest version of TFS/Test Agent(2015 - Update 3) and there are no other builds being run at this time. Often(maybe half the time), when the nightly job is run the step "Visual Studio Test Agent Deployment" fails with the following error: The job has been abandoned because agent Agent-XXX did not renew the lock. Ensure agent is running, not sleeping, and has not lost

dotnet test not creating test results folder

核能气质少年 提交于 2019-12-05 16:57:50
问题 As part of our ASP.NET Core 2.0 build process I have added a dotnet test command which I have added as a Windows batch file. Here is my command. dotnet test "MyProject.csproj" --no-restore --results-directory "MyProject\TestResults" --verbosity minimal And here is the output when run from the command line. So it all appears to work correctly, yet no test results / test output is created. 回答1: To output the test results from dotnet test, you can try pass -xml /some/path/out.xml or use the work

Can we build multiple gated check-ins in parallel?

主宰稳场 提交于 2019-12-05 09:26:25
Assuming we continue to use XAML build definitions for gated check-ins in TFS 2015 because the vNext system doesn't support them, is it still possible to get multiple gated check-ins running in parallel? I know that there is a Parallel option in the Build setup UI but I don't know if it can be applied to XAML build definitions as well, and what other constraints there are. Can you build in parallel on the same box (as long as it supports multiple agents)? XAML based gated builds of the same definition cannot be run in parallel. I believe that this is a deliberate limitation. The purpose of a

No agent could be found with the following capabilities: grunt

爱⌒轻易说出口 提交于 2019-12-05 09:01:48
When I try to queue a build on my on-premises TFS 2015 Update 1 I get the following error message: No agent could be found with the following capabilities: grunt I've already installed NodeJS and grunt-cli and they're in the path (i.e. they can be executed in cmd from any location). What am I missing? Go to your pool settings page: http://SERV_NAME:8080/tfs/_admin/_AgentPool and select your agent, verify that grunt is added as a system capability with the correct path set. If it's not there, you can manually add it as a user capability Something recalculates the system capabilities but I'm not

dotnet test not creating test results folder

你离开我真会死。 提交于 2019-12-05 03:14:05
As part of our ASP.NET Core 2.0 build process I have added a dotnet test command which I have added as a Windows batch file. Here is my command. dotnet test "MyProject.csproj" --no-restore --results-directory "MyProject\TestResults" --verbosity minimal And here is the output when run from the command line. So it all appears to work correctly, yet no test results / test output is created. Andy Li-MSFT To output the test results from dotnet test, you can try pass -xml /some/path/out.xml or use the work parameter, like this: dotnet test --work:"mypath/myresult.xml" . See below threads for details

On Premise Gated Check-in Fails with “The shelveset … could not be found for check-in”

非 Y 不嫁゛ 提交于 2019-12-05 02:24:38
I am having an issue with the new TFS 2015 Update 2 Gated Builds. After attempting a check-in the gated build queues just fine, every part of the build is successful until it reaches the last step of "Check in gated changes". When I look at the log for that step I get: [Error]The shelveset _Build_5427;Build\ad8fe058-f936-4908-91de-57e7bc6a2f9d could not be found for check-in When I look at the 'Get Sources' log, I see: 2016-04-01T19:11:12.3062092Z tf get /version:C6213 2016-04-01T19:11:13.2125013Z tf shelve _Build_5427 /replace 2016-04-01T19:11:13.3218610Z Successfully created new shelveset

build definition – only empty queue

こ雲淡風輕ζ 提交于 2019-12-04 22:45:06
问题 If I am creating a build definition, I can’t choose a Default agent queue. Not so long ago, I can create build definition which includes the default queue. I don’t know what the change was, that it doesn’t work anymore. If I go to edit a correct created build definition and then I try again to create a definition, I can choose the default queue. What is the reason for that? Editing an existing build definition before creating isn’t the solution, because I have many projects and some have a