All geek questions in one place

Build Errors TFS TF224003, TF215085, TF215076

I am using TFS2008 and VS2008. I run nightly builds for about 20 applications using a single build agent, and builds are scheduled for 1 or 2 hours. Most of the build succeeds, but 6 of them regularly fail with similar errors. Errors are either the first two below, or the third one:

  • TF215085: An error occurred while connecting to \ xxxx \ BUILDMACHINE agent: TF215076: Team Foundation Build on BUILDMACHINE computer (port 9191) does not respond. (Detailed message: the request was aborted: the operation was disconnected.) 04/11/2010 2:10:10 AM
  • TF224003: An exception occurred on the build computer BUILDMACHINE: the build (vstfs: /// Build / Build / 2632) has already been completed and cannot be started again.
  • TF215085: error connecting to agent \ yyyyy \ BA_WKSTFSBUILD: Team Foundation services are not available on the srvtfs server. Technical information (for the administrator): operation time

It seems to me that some kind of communication error, maybe the port is overloaded - can this happen? Should I distribute assemblies a little more? In the build definition, he says: “The build queue for the default built-in agent is in”, so I decided that I plan that they will start at the same time, they will be queued and executed sequentially.

Most of the suggestions that I found on the Internet for these errors are for all or nothing scenarios where no works at all, while my problem is most constructed, but some of them do not work consistently. Please note: if I plan to build through Team Explorer -> BuildDefinition -> Rightclick - Queue new build, they start without errors. Judging by the dates of the last successful builds of these 6 unsuccessful builds, I believe that this is the same as every night. (Right now I am editing assembly definitions to save failed assemblies so that I can get more information about the problem)

+4
source share
1 answer

It has been a while since I managed to create assemblies with TFS 2008, but I believe that I remembered that I ran into memory problems if too many were running on the same server. There are several parallel flags that you can use with MSBuild that can speed it up. I believe that if there is too much recursion (too much nesting of solutions), this can cause some timeouts like this. You can also consider removing agents and re-creating them, especially if the same assemblies are performed in some agent workspaces, but not in others. It looks like you said that some assemblies fail consecutively, which in TFS 2008, I believe, are displayed directly to specialized agents. Try the same builds using different agents and see what happens.

0
source

Source: https://habr.com/ru/post/1306656/

More articles:


All Articles