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?
Related
This question already has answers here:
Jenkins: remove old builds with command line
(12 answers)
Closed 7 years ago.
I removed old build folders from the build directory in Jenkins expecting them to be removed in the UI, unfortunately whilse these build directories are gone, their UI link still exists. I now have two questions:
How can I get rid of the defunct links in the UI?
How can I delete old build from cli and have it reflected in the UI?
A better way to remove old builds is discard-old-build plugin where you can specify how many builds you want to keep and all older builds are discarded.
You must either restart Jenkins or reload the data, in order to reconcile the UI with its back end. There is no other way.
If you have access to the "Manage Jenkins" menu there is a link to "Reload Configuration from Disk", which is a little less invasive than a restart.
Keep in mind that the system will be not usable for a few seconds while the data is reloaded, just like during a full restart. If you have a lot of builds, this might take a little. So, make sure that this is ok with the other users of your system.
Ever since we upgraded to 1.614 we have a problem with a certain hierarchy of tasks.
Two tasks are being stuck in "pending" every once in a while.
One task is descendant of the other and we indicate:"Block build when downstream project is building"
Notice that it does not say "Downstream project <> ..."
I have tried to upgrade again and we are currently on version 1.616
To solve this I cancel one of the tasks manually and the other one starts to run, but they are stuck until I notice that.
Can I prevent it from happening or at least auto cancel somehow when it happens?
Re "Can I [...] auto cancel somehow when it happens?"
See Build-timeout Plugin:
This plugin allows you to automatically abort a build if it's taking too long. Once the timeout is reached, Jenkins behaves as if an invisible hand has clicked the "abort build" button.
Seems like there is an issue in Jenkins that should was solved in 1.618
Problem did not reoccur after upgrading
Somehow our TF builds stopped working. When triggered, the build stays within the queue and does nothing. The build was also triggered with high priority.
We have also checked the system events, but there are no TF related errors. We have also restarted the IIS site of the TFS - no success.
Any ideas?
I assume you've already checked to make sure your build agent is running. If so, there's a good chance you've run into a bug I've seen before. If this is the case, do you have the latest updates for TFS? If this is the bug I'm thinking about, it causes the build agent to appear "reserved" when it's not. Getting the latest updates should address that particular issue. I don't know what version of TFS and what updates you have.
Closed. This question is not reproducible or was caused by typos. It is not currently accepting answers.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Closed 7 years ago.
Improve this question
I would like to disable multiple check-outs for our TFS projects. Here is how I expect it to work:
Bob checks out File1.cs.
Joe double-clicks on File1.cs in his Visual Studio Solution Explorer and tries to modify it buts sees an error message saying that someone already has that file checked-out so he cannot check it out.
I've tried setting it up like this in Visual Studio for both Bob and Joe:
Within Team->Team Project Collection Settings->Source Control...->Workspace Settings Tab I changed the default workspace type from "Local (recommended)" to "Server".
Within Team->Team Project Settings->Source Control...->Check-out Settings Tab I changed Enable multiple check-out to be unchecked.
Within Source Control Explorer->Workspace Combobox->Workspaces...->Edit...->Advanced->Location I changed "Local" to "Server".
Still, however, Bob and Joe can both check-out the same file at the same time. Is there some other configurations options that need to be set?
The issue (as pointed out by Edward Thomson) was that step 3 had not been performed on all of the users' workspaces.
You can also uncheck Enable file merging and multiple checkout in Team Project Collection Settings.
But you have to do this to any type of file you want.
http://msdn.microsoft.com/en-us/library/ms252452(v=vs.100).aspx
I'm using the Build Explorer to delete our project's builds. It's taking forever because it's 'timing out' trying to delete the label and drop location (now that the drop location doesn't exist any more).
So, I'm hoping to do this via the command line to see if I get more love.
Is this possible?
Yes it is, see the following HowTo on MSDN.
How to: Delete a Completed Build (Command-Line)
However, I'm not sure that this is going to improve the situation for you as it basically does the same server calls that the UI does. Give it a try anyway. In the meantime I'll go ask a few folks and I'll edit this answer if we come up with anything to help you with your timeout issues.
The TFS Build Manager utility will let you multi-select and delete. It still works serially but at least it's only one manual step.