I'm currently running TFS 2013 on one Windows Server 2012 box and TFS Build 2012 Update 4 on another box. My question is if I upgrade my TFS Build Server box to utilize TFS Build 2015, will I need to upgrade my TFS 2013 Server as well?
Also, what about the opposite? Can I upgrade my TFS 2013 server to TFS 2015 and still use my existing TFS Build 2012 Server which is using web deploy to build and publish to various other servers on our network?
Yes, TFS Build 2015 and Build vNext require your main TFS server to be at least 2015.
The other way around, TFS 2015 can talk to Team Build 2010, 2012, 2013 as well as the new 2015 build agents of course, as long as they're updated to their latest service pack and update version.
Upgrading your TFS 2012 build server would not be too hard either, depending on the amount of customizations made to the build workflows.
Related
I was working with Team Foundation Server 2015 where I had some releases configured for some environments (env1, env2, ...).
I installed TFS 2018 in a different machine. I migrated the code and I have completed the creation of a build definition.
I'd like to configure a release, using the old TFS 2015 environments. Can I install a TFS 2018 Agent, in the environments where I had installed the TFS 2015 agents?
In this way both of the agents would work without issues? The TFS 2015 Agent would work with TFS 2015 and the TFS 2018 Agent would work with TFS 2018 (both in the same machine).
I want to do this because my team is still working with TFS 2015, but as I am still setting up and testing TFS 2018 build/releases, I'd like TFS 2015 to work flawless (whithout any issue) while I am setting up and using TFS 2018 (with TFS 2018 Agents).
Different versions of agents can easily work on the same machine. As long as you keep the rule of thumb of 1 cpu core for the system and 1 cpu core per agent.
I have had multiple versions of agents running before on the same build machine without any issue. The only problem would be to try and connect an agent with 1.* versions to TFS 2018, since that wouldn't work, but since that is not what you are asking for, I would say that you are good to go :-)
We are currently running TFS 2012 with a 2012 build server and would like to upgrade to the latest TFS.
According to this link, 2012 Xaml builds are only compatible up to TFS 2013. However this link says that TFS 2018 update is compatable with Xaml builds. Would I be able to use my existing build server? Would I need to upgrade the current xaml builds that we use?
This can be confusing, so let me break it down a bit:
In general, a given version of TFS supports XAML build controllers for:
The current version
The previous version
TFS 2010 (for legacy reasons -- build servers running Windows XP, for example).
So, for TFS 2012, you can expect it supports TFS 2010 and TFS 2012 XAML build controllers.
TFS 2013 should support 2010, 2012, 2013.
TFS 2015 drops support for 2012 XAML controllers. This is also the last version for which a XAML build controller was released. TFS 2017 and TFS 2018 do not include a new version of the XAML build controller.
Therefore, TFS 2017 supports XAML build controllers for:
TFS 2010
TFS 2015
TFS 2018 RTM and Update 1 did not include XAML build support. XAML build support was reintroduced in Update 2, with the same compatbility matrix as TFS 2017.
XAML build is long-deprecated at this point. As soon as you are stabilized on a version that supports the new build system, you need to start migrating off of XAML build.
I am not aware of any documentation for upgrade of TFS. We are planning with New infra instead of inplace.
What are the pre-requists for same? what utilities i will require to move comeplete data from 2013 to 2018?
Most importantly, if i migrate from 2013 to 2018 will my users will loose all their workitems mappings to test cases in MTM or it will be same?
Upgrade is a full data transfer. You will have all data in the previous TFS.
As TFS 2018 only supports SQL Server 2017 and SQL Server 2016 (minimum SP1), upgrade SQL Server is necessary.
You need to go through article Upgrade your deployment to the latest version of TFS before doing upgrade. And follow the steps in article Upgrade scenario walkthrough for Team Foundation Server to upgrade your TFS. Summarize the steps here:
Prepare your environment. The first step is to check the system
requirements for TFS 2018. Upgrade SQL Server is necessary for your
scenario. Including SQL Server, you also need to check other system
requirements and prepare the environment.
Expect the best, prepare for the worst. You must have a complete and
consistent set of database backups in case something goes wrong.
Do the upgrade. Once the preparation is done, you'll need to install
the new version of TFS to get new binaries, and then run through the
upgrade wizard to upgrade your databases.
Configure new features. Depending on what version you upgraded from,
you may need to configure each team project to gain access to some
of the new features made available.
Here is a useful blog for your reference:
https://blogs.msdn.microsoft.com/rob/2016/12/22/upgrading-from-tfs-2013-to-tfs-2017/
Here are the System Requirements that you would have to cover to be able to upgrade. Some of them for your case are:
Client operating systems:
TFS 2018 Windows 10 (Professional,Enterprise) Version 1607 or greater
TFS 2013 Windows 8.1 (Basic, Professional, Enterprise)
Windows 7 (minimum SP1) (Home Premium, Professional, Enterprise,
Ultimate)
SQL Server:
TFS 2013 Update 4 - SQL Server 2014 or SQL Server 2012 (minimum SP1)
TFS 2018 - SQL Server 2017 or SQL Server 2016 (minimum SP1)
This means that you would have to upgrade your current TFS at least once prior going to TFS 2018. This would include upgrading your SQL Server and change your current OS. The options would be either TFS 2015 Update 3 or later, or TFS 2017 based on your preferences.
To be aware of what's new in the TFS systmes after TFS 2015, you could take a look at TFS page "What's new".
The similar question here: TFS 2012 to TFS 2018 Migration/Upgrade Path.
So you may do upgrade from 2013 to 2018, but you have to consider new requirements for Operating system and SQL Server, deprecated xaml build, new work item form. Any existing links between work items (requirements, tasks, tests) will be same.
In my opinion you can do inplace update if your OS in list with requirements. Detailed steps here: Upgrade to Team Foundation Server (TFS) 2017
I want to move the whole team project data(source files and work items…) from TFS 2008 to TFS 2015. Can anybody tell me the detailed step by step process, as I have never done migration within TFS versions?
You would need to do a upgrade for your TFS. Direct upgrade to TFS 2015 is supported only from TFS 2010 and newer. If your TFS deployment is on an older version than that, you will need to upgrade to TFS 2015 in multiple hops. For your scenario, you are on TFS 2008 you could upgrade to TFS 2010 or TFS 2012 first and then to TFS 2015.
The general process for upgrading an existing deployment of Team Foundation Server is to:
Prepare your environment. New system requirements may require you to upgrade hardware or software.
Expect the best, prepare for the worst. The single most important step you can take here is to ensure you have a complete and consistent set of database backups.
Do the upgrade!
Configure new features. Depending on what version you upgraded from, you may need to configure each team project to gain access to some of the new features made available.
Walk through an upgrade from TFS 2005 to TFS 2015.
I am testing the compatibility between TFS 2012 Source Control and TFS 2010 Build Agents, and I am glad to inform that they are compatible. I am wondering if there are any advantages to using TFS 2012 build agents. At this point, I have not found any information on advantages of using TFS 2012 build agents.
The 2012 build agent support the new Unit Test Runner, Lab Management environment, .NET 4.5 building, improvements in CodedUI, capability to trigger tests on a 2012 test agent, 2012 version of Code Analysis, improvements to Code Coverage and many many other things.
The main reason to support 2010 build agents, is to allow you to upgrade TFS from 2010 to 2012 without having to big-bang upgrade all build agents. When the next version of TFS comes, it will support the 2012++ and the 2012 build agents. It will no longer support the 2010 build agent.