My DevTest Labs video is up on Channel9
The video of my session at TechDays online is now available on Channel9, along with all the TechDay Online UK content Enjoy…
Uncategorised
Running Test Suites within a network Isolated Lab Management environment when using TFS vNext build and release tooling
Updated 27 Sep 2016: Added solutions to known issues Background As I have posted many times we make use of TFS Lab Management to provide network isolated dev/test environments. Going forward I see us moving to Azure Dev Labs and/or Azure Stack with ARM templates, but that isn’t going to help me today, especially when I have already made the investment in setting up a Lab Management environments and they are ready to use....
If I add a custom field to a VSTS work item type what is it’s name?
The process customisation options in VSTS are now fairly extensive. You can add fields, states and custom items, making VSTS is ‘very possible’ option for many more people. As well as the obvious uses of this customisation such as storing more data or matching your required process, customisation can also aid in migrating work items into VSTS from other VSTS instances, or on-premises TFS. Whether using TFS Integration (now with no support – beware) or Martin Hinshelwood’s vsts-data-bulk-editor (an active open source solution so probably a much better choice for most people) as mentioned in my past post you need to add a custom field on the target VSTS server to contain the original work item ID....
Typemock have released official VSTS build extension
Typemock have just released an official VSTS build extension to run Typemock Isolator based tests. Given there is now an official extension I have decided to deprecate mine, it is still available in the Marketplace but I would recommend using the official one The new Typemock extension includes two tasks SmartRunner Task The SmartRunner is a unit test runner, that can run nunit and mstest based tests. It handles the deployment of Typemock Isolator....
Fix for my Docker image create dates being 8 hours in the past
I have been having a look at Docker for Windows recently. I have been experiencing a problem that when I create a new image the created date/time (as shown with docker images) is 8 hours in the past. Turns out the problem seems to be due to putting my Windows 10 laptop into sleep mode. So the process to see the problem is Create a new Docker image – the create date is correct, the current time Sleep the PC Wake up the PC Check the create date, it is now 8 hours off in the past Now the create date is not an issue in itself, but the fact that the time within the Docker images is also off by 8 hours can be, especially when trying to connect to cloud based services....