I recently updated my TFS 2015 to TFS 2015 with Update 2. Everything went well but i wasn't able to queue builds anymore.
I logged in on the server and realized that I couldn't find my build controller anywhere (Still using XAML Build definitions).
The only thing i saw was this :
In my VS i saw this:
Is the build controller / agent completly gone from TFS with update 2? Did i miss something in the release notes?
Any way to repair my situation?
Related
We have TFS 2013 SP 4 (our existing version) and TFS 2017 (which is under testing for we are upgrading the TFS version).
My question is : Is it possible to work and test on both the TFS at the same time with the same workspace?
Business users are able to configure the new TFS 2017 and work there. However, when they are switching back to TFS 2013 (since we have not gone live with TFS 2017), it throws an 'Identity does not exist error'.
Has anyone tried it?
Is it even possible to test this way? Or shall we have one TFS version at a time for one workspace even for testing?
Thank you.
Anant
When upgraded TFS 2013 to TFS 2017(using TFS 2013 backup) on a new Server, the two servers have the same TFS GUID, which will confuse your Visual Studio clients.
You should avoid having two TFS up & running with the same set of GUIDs. And this is usually avoided by shutting down the old TFS server after the upgrade has finished and has been tested & verified.
We have migrated TFS2010 to TFS2015sp3 and we would like to use the existing TFS2010 build controller & agents (XAML) with TFS2015.
As a sample test, we did a clone of the existing TFS2010 controller and on the new machine we pointed the Project collections to the new TFS2015 URL.
I see the build controller and Agents in running state, but when I queue the build it keeps on waiting for build agent, even though the agents are online.
TFS 2015 still support XAML Builds as long as you use TFS2010/TFS2013 XAML Build controller.
Please make sure your build control version are the same as build agent version. So if you are using TFS2010 build control, you should also using TFS2010 build agent.
You could also create a new build control TFS2015 and build agent 2015, test if the build works properly.
Even though the build agent and control is online, you should also double confirm you have selected the right one in the drop list when you queue the build.
Besides, please also verify that your controller has "Maximum number of concurrently running builds" set to a number higher than 0. The default to number of agents can sometimes go wrong.
You set this on the controller properties in the TFS admin console.
You can also try remove the agent from the controller and add it again.
The new build system is pretty exciting. But...
I would like to know if there's any way to create a build definition with a gated checkin using TFS Version Control like it's available in XAML build definition?
Is it a hidden option or difficult to find? If not, is it possible to develop an extension to do that or must we wait for MS to support it?
Not currently, this is currently scheduled for Q4 2015 for vso and in Update 2 for TFS on prem.
Update 03/02/2016: this has been pushed back to Q1 2016 for vso but still in Update 2 for TFS on prem (which I would assume is also pushed back).
Update 31/03/2016: In Update 2, released 30th March, gated checkin support for TFVC was shipped.
This now shows on the Triggers tab of a build definition:
I was setting up a new build definition today and noticed there is an option 'Copy build output to the following Source Control folder'. I don't believe I have seen this before. It appears to me from searching google that it might be new as of TFS 11 (AKA TFS 2012) which I do not have installed on my system (or any system in my company network to my knowledge). My company uses TFS 2010 right now.
I went to another user who is able to view build definitions and it also was present when the build definitions were viewed.
This is what i see:
My questions:
1) Was this a part of TFS 2010 and I am just not remembering seeing it?
2) If this IS part of TFS 2010, how to enable this option (it is disabled).
3) If this is NOT a part of TFS 2010, how did it get there?
Yes, it is part of TFS 2010, but I have no idea how it got here!
I believe this is for those who use TFS 'as a service' (when you
have no file share to copy it to). According to
how-can-i-copy-build-output-to-the-source-control-folder
I have this in TFS/VS 2010 (SP1):
I'm trying to migrate from TFS 2012 Update 2 to TFS 2013.
Following the documentation I installed TFS 2012.2 on the new hardware, backed up/restored the databases, then installed TFS 2013 as an upgrade.
I can see the Team Project and the builds. The problem is when I right click a build to queue up a new one and click on the Parameters tab I just get a blank panel. My best guess is there was an error loading the parameters. Note those builds worked fine in TFS 2012.2.
If I create a new build from scratch and I use their new default template (TfvcTemplate.12.xaml) I still get the same error.
I don't see any errors in the output window or the event log.
It turns out it's a known bug with VS2013 connecting to TFS2013
The VS2013 hotfix has been released. Taken from here.
For future reference, this was fixed in Visual Studio 2013 Update 1 (see KB 2911573).