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
Related
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.
Currently, we are using TFS 2012 and we have a heavily customized build process as described below.
1. Build the source
2. Run an EXE as console to host WCF services
3. Restore databases on local sql server
4. Run functional test
5. delete databases
6. close the exe started in step 2.
7. Create an Installable exe using WiX ( Wix with custom bootstratpper)
8. Update version number file to TFS
Now we want to move to Visual Studio online from onpremise. Trying to setup a build process with Private Build agent. I have created an VM , installed and registerd agent. I do see agent name back in website.
When I go back to Visual studio and try to create new xaml build definition I am getting below error.
TFS22501: Creating a build definition requires a build controller be defined for this team project collection. There may not be any controllers configured or you may not have permissions to view them. contact your team foundation server administrator.
can somebody please help ?
If you're using XAML build, you have to use the old-style XAML build controller/agent. The VSTS agent is for the new build system.
I would strongly recommend migrating your builds to the new build system as part of your migration to VS Team Services, as the XAML build system is effectively dead.
I have upgraded to TFS 2015 Update 3 and can't find MSBuild in the available build templates. Only the following ones are available:
Any help to getting MSBuild installed would be appreciated.
I am on TFS 2015 update 2 and I don't see any MSBuild Build Templates available to me either. However, I would just use the MSBuild task after selecting the empty Build Template at the bottom of the picture you provided. I don't think a MSBuild Build Template exists for TFS 2015.
Also, whether or not MSBuild is installed is based on the Agent running your builds, not based on the build templates. You can see if your Agent can use MSBuild by viewing its capabilities under your agent pools at {tfs-name}:8080/tfs/_admin/_AgentPool
There's never been an MSBuild template. There has been, and still is, however, an MSBuild task. You can use the MSBuild task in any build definition.
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].
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