Move from GIT to TFS Version Control

I have dealt with a couple of clients recently who were very keen to get into the GIT repo's that are available in TFS 2013. The unfortunate truth is that GIT is not the "same" as the widely used TFS Version Control (TFSVC), SVN, VSS source control systems. Some teams tend to have a problem with this and, after numerous missing changes/files and problems with branching, commit vs pushing and merging issues, will inevitably ask : "How do we go back to what we know?".

There are tools to move from VSS & SVN to TFSVC and there are instructions to move from TFVC to GIT, but what about GIT to TFSVC? Well luckily, for a simple migration, you do not need any commercial or "3rd party" tools.

You do need to get your hand on GIT-TF and optionally the git client, and you are "a" for away.

1) Clone the repository

git clone http://<<servername>>:8080/tfs/<<Project collection>>/<<team project>>/_git/<<repo name>>

2) Replace the repository bindings

git remote rm origin

git tfs configure http://<<servername>>:8080/tfs/<<Project collection>>     $/<<team project>>/<<destination folder path>>

3) Finally check in the changes

git tfs checking --deep

Remember the --deep parameter - this will replay the commits as check-ins in TFS

The only thing you should be aware of here is that the check-ins will happen in chronological order, but the time will reflect the time and date that the check-in is occurring and not when they were committed into the GIT repo.

A Day of DevOps, Release Management, Software Quality and Agile Project Requirements Management Recap

Thank you for everyone attending the Microsoft event. There was a huge turnout which led to some interesting discussions.
My session around Work Management using TFS I mentioned some tools. I highly suggest that you go and browse the VS ALM Rangers solutions in general, but the work plug in that I used was Word4TFS.


I have also uploaded the slides here for the couple of people that asked for them:



 

TFS 2013.4 Stakeholder access

The stakeholder access has been mentioned a couple of times here and here by Brian Harry.

If you recall correctly the Limited access group means that if you are in that group, you do not need a CAL to access TFS Web Access. It also meant that you can only see a very scaled down version of web front end which basically  gave you access to the work items that you created.

Things have changed.. Now you have power!
Instead of the previous "Limited Access" group, there is now a Stakeholder group.
The allowed features have gone from "View My Work Items" to :

• View, add, and modify items on the backlog
• View team home pages and portfolio backlogs
• View, create, and modify work items such as stories, features, and bugs
• View, create, and save queries
• Sign up and receive alerts when changes are made to work items.

Where TFS has  been hiding in the developer realm within corporates, this move IMHO opens up TFS to adoption in big business, where getting everyone on board from a licensing perspective can be a huge expense.

Don't get me wrong, trend charts and pull requests in TFS 2013.4 CTP 1 are big, but you can have all the charts in the world, if the bar to entry for the stakeholder is too high, it is not going to give you the benefit that you need.
I can't wait until the CTP2 when the Stakeholder licensing is suppose to be finalised!

A Day of DevOps, Release Management, Software Quality and Agile Project Requirements Management.

Microsoft is organising two events for September, one in Cape Town and one In Johannesburg. If you are interested in seeing what TFS has to offer, feel free to register and come and have a look.
For those of you who will be joining us at the Cape Town event, I will be presenting the session just after lunch: Managing Work, Projects and Requirements with Team Foundation Server.
I'll be delving into:

• Requirements and Backlog Management
• Task Allocation, Prioritisation and Planning
• Agile Portfolio Management
• Task Boards and Kanban Boards
• Reporting and Integration
• Test Case Integration
• Project and Excel Integration

Hope to see you all there!

A Day of DevOps, Release Management, Software Quality and Agile Project Requirements Management

Are you looking to improve the way you manage software projects or release software? Perhaps you need some better processes for managing test cases and bugs? Join us for 2 half-day sessions in Cape Town and Johannesburg where we will focus on these topics and more.

Morning Session: Getting Started with DevOps, Continuous Delivery and Release Management

Audience: Developers, IT Professionals, IT Decision Makers, Testers, IT Managers Release management and DevOps have become an important part of the modern application lifecycle. This session will cover: Release Management and Automation, Release Pipeline and Approvals Treating Configuration as Code Working with Chef, Puppet and DSC Application Insights Cloud-Based Load Testing Production Debugging and Monitoring Leveraging Azure for DevOps and Dev/Test Environments System Center and TFS Integration

Afternoon Session: Improving Software Quality and Requirements/Project Management Practices

Audience: Business Analysts, Testers, Product Owners, Scrum Masters, Developers,
IT Managers
Delivering high quality software that meets users' requirements is a risky undertaking. Development and quality assurance managers, along with product owners and business analysts, need to be in a tight partnership in the war against software bugs.
This session delves into this and is broken into two parts.
1. Managing Work, Projects and Requirements with Team Foundation Server
Team Foundation Server provides a wide set of capabilities for managing requirements and work. These allow you to implement your own practices, or incrementally adopt the most agile or other practices that best fit your team.
Topics that will be covered include:

• Requirements and Backlog Management
• Task Allocation, Prioritisation and Planning
• Agile Portfolio Management
• Task Boards and Kanban Boards
• Reporting and Integration
• Test Case Integration
• Project and Excel Integration

2. Improve Software Testing with Team Foundation Server
Topics that will be covered include:

• Planning and Managing Test Suites and Test Cases
• Running Test Cases
• Logging and Managing Defects
• Web-Based Test Case Management and Execution
• Exploratory Testing
• Automated Testing

 

CAPE TOWN Date:    10 September 2014 Venue:    Crystal Towers Hotel & Spa, Century City, Cape Town Time:    09:00 - 16:00 RSVP:    Click here to RSVP Event ID: 1032593595 Call: 0860 22 55 67 Email: saevent@microsoft.com

JOHANNESBURG Date:    15 September 2014 Venue:    Microsoft Johannesburg Office, 3012 William Nicol Drive, Bryanston Time:    09:00 - 16:00 RSVP:    Click here to RSVP Event ID: 1032593593 Call: 0860 22 55 67 Email: saevent@microsoft.com

Delete Test Manager Test Settings

I was looking for a way to remove old test settings in Microsoft's Test Manager but was not having any luck finding a way to delete them.

I knew there was a way through the expensive API that TFS has, so I eventually resorted to creating my own little utility.
If you were stuck with the same problem, feel free to give this a go.

TFS 2013 Pre Build Script Assembly Version Updates

I was looking at a "simple" way to update the TFS build definitions and adjust the Assembly versions of the projects being compiled. I came across this article (http://msdn.microsoft.com/en-us/library/dn376353.aspx) leveraging the pre and post build scripts that are available in the newer build definitions.

The problem I had with the scripts included in the TFS Build Extensions is that it uses the Build Number or Label. This does not really make sense to me so I started hacking at it.
Fortunately it was not as big a task as trying to delve into the new build definition's workflow and trying to find the variables that "used to" exists.

If you are interested, I have posted the resulting PowerShell.
Simply add this to the TFS repository, and then reference it as a pre-build step in your build definition and you will notice that your AssemblyVersionInfo.cs files are updated before the build, replacing the revision to the changeset number.
This will give you a reference from the actual assemblies back to the code or changeset that they originate from.



Enjoy!

Release Management Event

Last week Microsoft hosted a Release Management for Team Foundation Server 2013 talk where I ran through managing releases using Release Management.

I am pleased to say that there was literarily not a seat available, and the audience was responsive and interested. This is obviously a topic that is on a lot of people's minds.

For more information, you can visit the official site.

If you are interested, I have uploaded the slides here.

We will have to try and schedule a similar event shortly

Thank you to all those that attended and participated, and to Microsoft for making it possible.