1111 MSTestRunner Users

I'm happy to see today that MSTestRunner Jenkins Plugin I wrote and use every day has pass the 1K users this month.

Many thanks to all the users and specially to those who left comments explain how to improve it.

Have fun using it and keep on testing.

Continuous Delivery of ASP MVC with Jenkins and MSDeploy

We have been using Jenkins to deploy our web application for a while using continuous deployment, that is we used to push our changes into our git repository, go into Jenkins and run the deployment job.
Last month after successfully working in this way we decide we can trust ourselves and our systems and move to continuous deployment (or more accurately continuous release).

The ingredients

• Jenkins (LTS 1.509.1) with the following plugins
• Jenkins GIT plugin
• Jenkins MSBuild Plugin
• JENKINS MSTest plugin
• MSTestRunner Plugin
• CloudBees Build Flow plugin
• MSBuild
• MSTest
• MSDeploy

We divide the deployment process into several jobs and connect them all together using CloudBee Build Flow plugin.

The Jobs

1. build & test - This job build and test both debug and release configuration of our web application
2. deploy - This job deploy our web application using MSDeploy
3. end-to-end-tests - This job run end-to-end test on our production web application using Watir web testing framework
4. continuous delivery - This job is a build flow job that simply run jobs 1,2,3 in order. If anything goes wrong it notify us.

What's still missing?

1. Staging - We are working on deploy our web application into staging environment and run the end-to-end test on it. This does not guaranty success but it does catch errors. 

In the next posts I'll go into details about each of the jobs.

MSTestRunner for Jenkins is now 1.0.0

I'm happy to let you know that my Jenkins plugin MSTestRunner has reach version 1.0.0
The major change is that the plugin now support running unit test containers (DLLs) in path that has space in it.
It was requested from people having path inside the workspace with spaces as well as people who want to run unit test that are not inside the Jenkins workspace and use full path.

This is also great place to say the plugin usage statistics show it is used by almost 1,000 developers.
Compare it to MSBuild plugin which has over 6,000 developers it mean 1 of 6 .NET developer run unit test in the CI server. This is nice statistics by itself :)

Thank you very much to all the developers who use this plugin and thank you very much for everyone who helped by contributing code or simply explain how it can be improved.