I'm trying to create a new Build Definition in TFS 2015 but when I get to the Process section there are no templates available for me to select. This server was upgraded from 2013 to 2015. I don't know if the templates existed in 2013. How do I get the default templates?
Update
Found TfvcTemplate.12.xaml here, added it to source control, clicked new browsed to it and still nothing.
Ask the admin to check your account's permission in the Security of XAML Build Definition, it seems you don't have View build definition permission:
Related
We just upgraded from TFS 2013 to TFS 2017 and I was excited to go in and create a new build definition, but I can't seem to do it at the collection level. I can only create a new build definition once I've selected a project and then when defining the Get Sources page I can't seem to access other projects within the collection. The highest level it will allow me to get is the current project. In the Repository drop-down the only option is the current project. How can I create a new build definition across projects in TFS 2017?
The TFS build is project level for now, it's not able to create a build definition at collection level and across projects. For 2015 you could, instead of using the trigger path '$/{team project}', also insert just '$/', which would result in that the continuous integration build triggers on all check-ins in that team project collection. It's more like a backdoor.
However, In TFS 2017, it 's no longer possible to freely edit this field, and that you can only add a trigger for the team project that the build definition resides in.
There had been a uservoice and got started:
VSO build vnext: share build templates between projects
https://visualstudio.uservoice.com/forums/330519-visual-studio-team-services/suggestions/8468566-vso-build-vnext-share-build-templates-between-pro
As a workaround you could export your existing build definition in the project to other project. However, this just avoid you manually duplicating the definition in another team project. It's not able to get source from another project which different with the build definition belongs to.
There is an Export/Import Build Definition extension in Visual Studio Marketplace you can use now. Also available from within the TFS2017 update1 Build Definitions web UI:
.
Is it possible to change the settingd for TFS 2017 to only have Team foundation Server version control available (disable git) and only have CMMI available for the work item process? I am using the web interface.
You can delete the process templates from within Visual Studio.
You can't disable Git support, but you can easily create a new TFVC repository in an existing team project if someone chooses incorrectly.
Unfortunately, it's not able to customize the Create team project process. You could not directly disable the options both for Process template and Version Control.
You could create a uservoice, TFS PM will kindly review your suggestion.
Is it possible in TFS 2015 on-premise to modify a collections process templates? According to the article here, there should be a "process" tab on the web interface, collection administration page. This document is for 2015 but is a little old. Should this feature be available for 2015 on-premise upgrade 2? Am I missing a permission?
https://www.visualstudio.com/docs/work/customize/customize-work#team-projects-and-processes-team-services-
Just as the article mentioned, the settings are with VS Team Service. Team projects and processes (Team Services) And there is no “process” tab on the web interface for TFS2015.
Scroll down the page and you will see Team projects and process templates (TFS)
When you work with an on-premises TFS, you customize your work
tracking experience through one or more XML definition files. You can
start by customizing a process template and its XML definition files,
and then create a team project based on the template. Or, you can
simply make modifications as needed to add customizations to the work
item fields, work item types, and other objects that support tracking
work.
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).