We have TFS 2012, and have a lot of projects created back in version 2008 of TFS.
Is there a way of finding the name of the TFS project template that was used when creating the TFS project?
Thanks,
Thomas
Short answer: no.
You may check the Work Item Types available in a project and infer the Process Template used, e.g. "MSF for Agile Software Development" had a "Quality of Service Requirement".
TFS Team Project Manager on CodePlex is a free tool which will inspect all your team projects process templates (even if they're customized) and tell you which process template was most likely used to create that Team Project (and give you a % confidence in the match). You can even give it additional "source" process templates, such as your company custom process template, and it will tell you which projects were created with it.
I found a way for finding the template name from a SQL query. However, this will only list those projects that were created in TFS2012
USE Tfs_DefaultCollection
SELECT tbl_projects.project_name AS [Team Project], tbl_project_properties.value AS [Process Template]
FROM tbl_projects INNER JOIN
tbl_project_properties ON tbl_projects.project_id = tbl_project_properties.project_id
WHERE (tbl_project_properties.name LIKE '%Process Template%')
Related
Good Afternoon,
I'm a little new to the Release Management Department and I've been tasked with converting our Release Management 2013 templates over to 2017. I've ran into a road block recently that I've been unable to figure out how to proceed, and wanted to consult the experts for tips or suggestions.
The most major issue is that Release Management 2017 doesn't offer the ability to setup Environment Tags, meaning I can't setup a "Production" environment and tag all of our production IIS servers in it in order to run a single command against all the servers. This hinders me greatly.
I've done research on this issue and have come to two possible work arounds. Either 1) Creating a release template for each IIS Site or 2) Creating a Release Template for each Environment (Test/Stage/Prod). The problem here is that we managed over 100 different IIS Sites and Databases, so creating an individual template for each site would be...astronomical. Whereas creating one bulk template for each environment could lead to issues down the line if we needed to release a specific site.
I figure that we are not the only company that work with this many IIS Sites, and that someone has to have figured out a better solution that the two above. Do we need to look elsewhere other than TFS2017 (With built in RM Features)?
I appreciate any and all advice on the issue.
The tasks you'd be using to target your servers (such as "PowerShell on Target Machines") take a list of servers to execute against. You can store the server names in a variable on the release definition at the environment level.
In TFS 2017 Update 1, you'll be able to store related variables in variable groups and share them across release definitions.
how do I delete a Team project from TFS?. I am using VS2012.
The situation is that a Team Project was created with the wrong name, and another one was created with the right name and all the code has been checked into that.
I just want to delete the wrongly created one. I cant find any specific help on this, although there are articles on how to do it on if your TFS is hosted on visualstudio.com.
Apologies if this is a noddy question but I have looked for the answer and cant find it...
Thanks in advance
Jonathan
You can use the "TFSDeleteProject" command line tool to delete the team project.
Here is the usage:
TFSDeleteproject [/q] [/force] [/excludewss] /collection:URL TeamProjectName
TFSDeleteProject permanently destroys the team project, after which it cannot be recovered. You should backup all important project data before using TFSDeleteProject.
Required permissions
To use the TFSDeleteProject command, you must be a member of the Team Foundation Administrators security group or the Project Administrators security group.
You can use the link to delete the team project using the administrator console.
My issue is that I cannot select a build process template after migrating to TFS/VS2012.
I managed to google and find one article which suggest the same problem here,
Possible Bug
Any ideas how I can get the dropdown to load the Build Process Templates or why they may not be getting loaded?
Also, I am able to click New->Copy Template, and copy successfully, but it never populates the dropdown list after accepting.
Possibly the same issue
I recently ran into the same problem but not related to upgrading the server. We were not able to see build process templates when trying to add a new build definition. We are in TFS 2012. This team project also appeared not to have any build definitions. That was expected though because we had not yet used the TFS builds on this team project.
The problem was caused by someone with admin rights setting the "View build definition" and the "View Builds" access rights to Deny for everyone.
By just setting that back to allow on the TFS group, we suddenly could see the build definitions and also were able to select build process templates.
It was really strange that it let us add new build process templates, but we couldn't select them.
Sooo...
I was finally able to get the templates loading by doing the following.
Unmapped the entire TFS project which had been mapped in a sub folder and not at the root.
Deleted files from disk completely
Remapped the TFS project, this time from the root TFS project level
Accepted the "get"
After doing this my build definitions loaded and worked. (Seems to be a mapping issue...bug...)
This may be an extream solution and I am still not sure what happened but it now works.
I am having a problem where My Eclipse 9.1 is not able to connect to multiple projects in 2010 using the Team Explorer Everywhere plugin. If I try to connect a second project, it disconnects me from the first one. I can not find any way to be able to pull down multiple projects like I was in TFS 2008.
Any Ideas?
This is as-designed. Team Explorer Everywhere can only connect to a single Team Project Collection at a time. There are myriad reasons why this is the case, but all are to preserve the notion of atomic operations against the server. Some operations (for example, check-in) simply must be scoped to a single server instance in order to make sense.
Since a single changeset is atomic in TFS, an attempt to check-in multiple pending changes either all succeed or all fail. Consider if you had pending changes from two different servers: you cannot commit all these changes as a single changeset - one server could reject your check-in due to conflicts, while the other could proceed successfully. This is, at best, confusing, but most likely actually leaves your projects in an inconsistent state since there may be dependencies between these projects. Since there are distinct changesets for each server, the UI must reflect that.
After much deliberation and experimentation, we concluded that the best user experience is simply to have an experience where you can import projects from multiple TFS servers, but you must select which server you want to work with in the UI by selecting which one is currently "online". All TFS functionality is available for the online server which a limited subset of the TFS functionality is available to the other projects.
We would recommend that you consolidate your Java projects to a single Team Project Collection if you need to import all of them.
This behavior is unchanged from any previous versions of the software, including before the acquisition of the technology by Microsoft (when the product was still part of Teamprise Client Suite.)
Also note that the scope of commands available to "offline" projects has increased dramatically in TFS 2012 thanks to the new Local Workspace functionality.
We have a lot of build definitions on our TFS 2010 for the same 'Team Project'.
But not all build tasks are relevant for developers or they haven't the privileges to queue a new build.
Is there a way to manage the definitions with folders / tags or something else to keep it simple? Otherwise the developers will lose the overview if tens of build definitions are available.
thank you and kind regards,
danny
There is now a VS 2010 plugin that kind of does this. We've just tried it and it really helps manage the build definitions but it requires you to have a naming convention in place
It is currently not possible. You can vote on https://connect.microsoft.com/VisualStudio/feedback/details/582949/tfs2010-team-explorer-multiple-build-folders-for-team-project to have it in the next version of Visual Studio (aka Dev11).
The more votes, the more likely it gets higher on the backlog.