Using Visual Team Services's build system to achieve a Continuous Delivery pipeline

February 15, 2017    VSTS DevOps Continuous Delivery

Using Visual Studio Team Services’s (VSTS) build system to achieve a Continuous Delivery pipeline Presentation

originally posted on on 2015-11-10

I had the honor and pleasure of giving my first presentation at an event at South Dakota Code Camp on November 7th, 2015. Thanks to the organizers and sponsors, I’m looking forward to next year already.

I talked about the importance of Continuous Delivery in today’s development practices and how it helps us get quality code to our users quicker and more reliably using automated processes. Microsoft’s build system has improved immensely in the last year and one of my goals was to show what I’ve learned, what’s possible and prompt them to try it out themselves.

  1. Microsoft has greatly improved their build system.
  2. You can get started quickly, but there is a lot of depth to dig into.
  3. Visual Studio Online (now VSTS) gets the latest code, then it is rolled out to on premise TFS installs.
  4. You can build non-Microsoft technologies with it and run NodeJs NPM, Bower and Grunt/Gulp tasks in it. iOs, Make, Maven, Java, Ant and more.

I’ve added some code to my GitHub project and added a lot of notes and links in the readme.

My presentation slides are still up on Prezi

** EDIT: I recommend the new (December 24, 2015) Continuous Delivery With Visual Studio ALM 2015 (the blog post for step by step instructions on how to do Continous Delivery, testing, deployment, setting up test environments and even running Selenium tests in the build (something I failed to figure out on my own). They even show how to setup SonarQube and using these ideas on a “real” project. **

The code has some approaches I’ve learned about writing Selenium tests to do automated UI testing of a web project

I did run into some snags trying to get the Selenium tests running in the Azure build setup, but I’ll keep digging into it. I have a lot to learn about WinRM remote Powershell, setting up trusted hosts and configuring things. Thankfully, the build configuration web UI is much simpler. I tried following this

Here are a few more links, but see my readme for a lot more:

Me Presenting -

comments powered by Disqus