I have configured a new build controller
Current Controller config:
Windows server 2008 R2
TFS : Tfs2012.Update4
Visual studio 2015
New Controller config:
Window server 2016 standard
TFS : Tfs2012.Update4
Visual studio 2015
If i trigger a build to current controller if there is a error it throws the errors.
But if i trigger a build to new build controller build get stuck at some point and never comes out. It do not throw any error.
Moreover, no logs get copied to TFS server, only empty folder gets created with Defintionname_time.
I tried manually building the solution using msbuild command it get succeeded.
I am new to TFS build please help.
Window server 2016 is not supporeted for TFS 2012.
Please refer to Requirements and compatibility for details.
You should consider migrating to the latest vNext build system TFS 2017 or even TFS 2018.
The xaml buil system is too old and not supporeted by TFS team.
Reference Why You Should Switch to Build VNext
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.
I'm trying to import modified WITs to a existing project. But, It was showing the below error:
Microsoft.TeamFoundation.WorkItemTracking.Server.ProvisioningImportEventsCallback
Earlier it was working fine. But, now the issue started.
What could be the possible solution for this? I just wanted to upload WITs through Command prompt(witadmin.exe) only. Any hints/information would help
From your description, you are trying to use VS 2015 to connect to TFS 2017. Please check documentation Import, export, and manage work item types:
If you are connecting to TFS, you must use the same version of Visual
Studio or Team Explorer as TFS. For example, if you connect to a TFS
2017 instance, you must connect from Visual Studio 2017 or Team
Explorer 2017.
TFS 2018 and TFS 2017
Visual Studio 2017 or Team Explorer 2017 client:
%programfiles(x86)%\Microsoft Visual Studio\2017\Community\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer
or, TeamExplorer, Professional or Enterprise in place of
Community, depending on the version you've installed.
You should install VS 2017 or Team Explorer 2017 to run this command. Although VS 2015 could run witadmin command against TFS 2017 sometimes, there would have unexpected issue.
However, I found the solution for this issue by myself.
Clear the Team Foundation cache from your server and the user system from the below path:
C:\Users\\AppData\Local\Microsoft\Team Foundation\7.0 (or 6.0)\cache
Delete everything from the cache folder and restart the server\system. Then Login to the server. Now, you won't get any error for uploading [WITs] using command prompt.
Follow the procedures as given in Microsoft Site.
https://learn.microsoft.com/en-us/vsts/work/customize/reference/witadmin/witadmin-import-export-manage-wits?view=tfs-2018
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.
When we are trying to queue a build with some coded UI tests, TFS 2015 complains about test agent not being of the correct version.
No agent found in pool 1 which satisfies the specified demains:
Agent.Version -gtVersion 1.94.0
I've downloaded and installed the Agents for Microsoft Visual Studio 2013 Update 5, but I'm not sure if it's the latest possible version we can get.
I'm 100% pretty sure TFS sees our agent.
Is there a way to ensure we have this 1.94.0 version? And where can I find a download link for it? Or maybe, the problem is not with the version?
It's looking for a build agent which version is equal to 1.94.0 rather than the test agent version. Please download the latest build agent from your TFS web portal and configure it.
If you are running tests using Build vNext tasks and want to install agents from a local directory, you need to download Agents for Microsoft Visual Studio 2015 Update 3 - Click on "Tools for Visual Studio 2015" and then select "Agents for Visual Studio 2015" from the left navigation bar.
Or you can add a Visual Studio Test Agent Deployment task in your build step. This task will deploy “Test Agent” to all the machines and configures them automatically for the automation run.
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