I have ported over all of my build customizations from TFS 2010 to the new TFS 2013 build process template. What would be the best approach to upgrade the old build definitions to the new template while retaining the settings (i.e. configurations to build, project, ect.) from the old one?
If your arguments are still the same, you should be able to open your existing definition and just apply the new template. All of your original settings should remain intact
Related
I have been working on TFS 2017 update 3 from past couple of years and now I have started working in new team where they are using TFS 2015.
In TFS 2017 Web, all the Build Definitions we had we used to keep\save them into their respective folders as their was option of Manage Folder present under Build Tab but here in TFS 2015 Web, I don't the see the option of Manage Folders and have to keep\save all the Build Definitions under one tab.
Is there any extension available in the marketplace or way by which I keep all the Build Definition in a more organized way in TFS 2015?
I am afraid Manage tfs2015 doesnot support Manage Folders feature. And I failed to find an extension that was available on the marketplace to achieve this.
You need to upgrade tfs2015 to a newer version in order to use the Manage Folders feature.
You can check out below document for more information:
Upgrade your deployment to the latest version of Azure DevOps Server
We installed the newest TFS Server (TFS 2018 Update 2) which should run xaml builds.
After the update, we started our agent, but our xaml-controller is still offline and I don't know how I start this again..
Any ideas what we can do?
Yes, you can now upgrade to TFS 2018 Update 2 and continue to connect
your XAML controllers and run XAML builds. When we removed support for
XAML build in TFS 2018 RTW and Update 1, some of you could not upgrade
due to having legacy XAML builds, and we want to unblock you. Although
TFS 2018 Update 2 supports XAML builds for your legacy builds, XAML
build is deprecated and there will be no further investment, so we
highly recommend converting to a newer build definition format. See
the Evolving TFS/Team Services build automation capabilities blog
for more information about XAML build deprecation.
When you upgrade to TFS 2018 Update 2:
If you have any XAML build data in your team project collection,
you'll get a warning about the deprecation of XAML build features.
You will need to use VS or Team Explorer 2017 to edit XAML build
definitions or to queue new XAML builds.
If you need to create new XAML build agents, you’ll need to install
them using the TFS 2015 build agent installer.
XAML Build Controller/Agent info is now under Additional Tools and Components > XAML Build Configuration in the TFS Administration Console. Make sure your build services on the same server as your application tier. You possibly didn't re-configure your XAML build services after the upgrade. Try this and then check again.
Thanks #PatrickLu-MSFT!! through your help, we found a workaround.
Now we use one server for the Source Control etc. (TFS 2018) and another server only for the xaml-app-controller with TFS 2015.
So we can build our projects, and have time to create new build definitions.
We currently use TFS 2013.
I'd like to do a POC where I can create some build definitions in TFS 2015 where it would get the source from our existing TFS 2013 server. Once the boss sees how much easier it is to manage our builds from TFS 2015, I'm sure he'll give us the go-ahead with upgrading the existing TFS 2013 to TFS 2015.
Is this even possible?
You could write a PowerShell script or some batch files to leverage tf.exe in order to map a workspace / clone a repo (depending on whether you're using TFVC or Git) as part of a build. Or just put the tip of your source code into the "demo" environment and build from there. The latter option is going to be much faster.
We are trying to upgrade to TFS2015 and have done a test configuration for TFS 2015.
I have noticed that if we create a new project in TFS2015 the project is all empty, it does not even have the BuildProcessTemplates folder.
Can anyone guide me on how to get the Default build definition?
You are right that there is no BuildProcess Template folder created when you create a team project in TFS 2015.
If you have configure XAML build, you can download the build process template by creating a XAML build definition:
By the way, you can also check the new build system in TFS 2015, which is based on windows services, and doesn't need build process template. https://msdn.microsoft.com/en-us/library/vs/alm/build/feature-overview
I use Visual Studio 2015 and TFS 2012. In Team Explorer, it is possible to manage Builds and Build Definitions. Since VS2015, the section Build Definitions is named "XAML Build Definitions". I would like to put xaml build definitions in source control. Problem is I cannot find the build definition files on disk. Anyone knows where they are ?
Thanks
You can download build process template and add it into source control, but you can't version-control build definitions.
In the new build system coming with TFS 2015 you can see the full history of the changes to your build definition. The feature that is currently missing is the ability to undo or rollback to a previous revision. Check https://visualstudio.uservoice.com/forums/330519-team-services/suggestions/2037625-provide-a-way-to-version-control-build-definitions
Just in case anyone needs to access the XAML Build Definitions parameters. They are saved in the TFS database, table: [dbo].[tbl_BuildDefinition].