Normal Priority Builds Will Not Build in TFS 2010 [closed]

Closed. This question needs details or clarity. It is not currently accepting answers.

---

Want to improve this question? Add details and clarify the problem by editing this post.

Closed 2 years ago.

Improve this question

I have two build processes setup in TFS 2010. One build starts when any developer checks code into TFS. The second build runs every night at 12:30am. I can see the builds have a priority of Normal in the queue. However no queued build ever is run until I change the priority to high. They will sit in the queue forever until the priority is changed.

It appears there is a normal priority build in the queue that is stuck. However I cannot find it. I can select Any Build Definition, Any Status, and Any Build Controller and not see anything but these builds queued up. I can run them all and the next day I have queued builds again. I say this because I see the Build Service is configured for port 9192, 开发者_运维知识库which leads me to believe there is or was another Build Service on port 9191.

Any idea how to resolve this issue?

---

I had this same problem where only builds that were "Above Normal" or High priority would actually build.

I tried restarting the build service, controller, and agents with no effect. There were no errors in the Event Log.

It turned out that there were 2 rows in the tbl_BuildQueue table for build definitions that I had recently deleted. Changing the status of those rows from 2 (Queued) to 16 (Cancelled) fixed the problem for me.

Here are some links that helped me figure this out:

http://networkprogramming.wordpress.com/2010/10/27/default-controller-cannot-be-deleted-because-there-are-builds-in-progress/

http://blog.hinshelwood.com/ghost-team-foundation-build-controllers

---

I ended up removing a normal priority record from the table tbl_BuildQueue. This appears to have resolved the problem.

---

Deleting rows from 'tbl_BuildQueue' fixed it for me.

---

I had a similar issue with builds not... building! Had to restart the controller/build agent which seemed to fix it.

While you're in there, the Build Configuration checks the Event Log for errors, anything showing up?