A user wanted to know how to list all of a certain users workspaces across all machines without having to install TFS Sidekicks. It is a simple command and you can use the * wildcard for the owner or computer.
tf workspaces /owner:UserName /computer:* /collection:TFSURLIncludingCollection
This will produce a nicely formatted list of workspaces for that user. This could be used in a script to delete workspaces for a user but with Sidekicks around that is my preferred option as an administrator.
Thursday, January 29, 2015
Tuesday, January 27, 2015
TFS Wildcards and History
A coworker had asked me the other day if it was possible to get a list of changes for a subfolder with a certain name. This subfolder lets call it Views is located in multiple places on the branch.
I tested out to see if you could place wildcards in the itemspec path. The answer is no you cannot. You can only place wildcards at the end. For example this does not work:
tf history -server:http://tfs/tfs/MyCollection $/MyProject/Branches/Database/MSSQL/*/Views/* -recursive -format:detailed –noprompt
This does work:
tf history -server:http://tfs/tfs/MyCollection $/MyProject/Branches/Database/MSSQL/* -recursive -format:detailed –noprompt
In the end you would have to write a script to sort through the files in each changeset and filter out just the changesets returned that had /View/ in the path. If I get some time to write this script I will post it. Hope this help you.
I tested out to see if you could place wildcards in the itemspec path. The answer is no you cannot. You can only place wildcards at the end. For example this does not work:
tf history -server:http://tfs/tfs/MyCollection $/MyProject/Branches/Database/MSSQL/*/Views/* -recursive -format:detailed –noprompt
This does work:
tf history -server:http://tfs/tfs/MyCollection $/MyProject/Branches/Database/MSSQL/* -recursive -format:detailed –noprompt
In the end you would have to write a script to sort through the files in each changeset and filter out just the changesets returned that had /View/ in the path. If I get some time to write this script I will post it. Hope this help you.
Tuesday, January 13, 2015
Using TFS 2013 Update 4 License Change for Agile Teams
We are in the process of upgrading to Update 4 and were figuring out how the license changes affect us (was hoping for costs savings.) They don’t and probably won’t save us on MSDN costs. Read on to see how it could save you.
I was hoping we could drop them down to Basic (TFS CAL) but the environment thing stops that. With Basic access a product owner could plan and prioritize user stories for their team but not features. I guess features is what Microsoft deems advanced planning. This would be a big cost savings to some companies.
Our next layer is product manages themselves. While they don’t hop on the development environments that still need to be able to plan and prioritize at the feature level. With Microsoft’s new license structure nothing changes for us. Again to get just that feature requires an MSDN license. That is pretty costly unless I can get them to use the feedback or storyboarding features.
They can prioritize by using the Team add on in Excel. To do that just have a query of the features and make sure the Stack Rank is one of the columns. They can then modify the stack ranks to prioritize the work items. Once that is done a publish up to TFS will update it for the teams to work from.
This could become cumbersome as working with the stack ranks is not easy for a large number of work items. The PM’s at my company need to be able to work fast so this will not fly. Hopefully some one else out there will be able to do this and same some $$.
Happy ALM’ing!
Development
All of our developers and testers have an MSDN Premium or Ultimate. This covers them not only for TFS but also access to all there test environments and whatever software they have installed. They will remain at the Advanced access level.Product Management
The next layer of user is the product owner. Our product owner sits with each team and helps to manage and groom the backlog. They also validate work is done which means they use development environments. That being said they will continue to need MSDN Premium.I was hoping we could drop them down to Basic (TFS CAL) but the environment thing stops that. With Basic access a product owner could plan and prioritize user stories for their team but not features. I guess features is what Microsoft deems advanced planning. This would be a big cost savings to some companies.
Our next layer is product manages themselves. While they don’t hop on the development environments that still need to be able to plan and prioritize at the feature level. With Microsoft’s new license structure nothing changes for us. Again to get just that feature requires an MSDN license. That is pretty costly unless I can get them to use the feedback or storyboarding features.
The Stakeholder
This access level is free and allows the editing and creating of work items. If your product managers are willing to do some work in Excel this will provide your company with some cost savings.They can prioritize by using the Team add on in Excel. To do that just have a query of the features and make sure the Stack Rank is one of the columns. They can then modify the stack ranks to prioritize the work items. Once that is done a publish up to TFS will update it for the teams to work from.
This could become cumbersome as working with the stack ranks is not easy for a large number of work items. The PM’s at my company need to be able to work fast so this will not fly. Hopefully some one else out there will be able to do this and same some $$.
Happy ALM’ing!
Subscribe to:
Posts (Atom)