I remember when Brian Keller (who was a DPE at the time) first released a VM that had TFS and Visual Studio installed and configured, along with a set of hands on labs for experimenting and learning about the Microsoft ALM Stack. Over the years, the VM (and its siblings) affectionately became known as “Keller VMs” or “BK VMs”. Being an ALM consultant, I know how hard it is to set up a demo environment – not just installing and configuring TFS and Visual Studio – but also adding meaningful data to play with. Brian’s VM was easy to run and was great for just kicking the tires.
Today we’re excited to announce that we’ll be hosting a preconfigured VM, developed by Brian’s DPE successor Sachin Raj from Microsoft, that showcases the Microsoft DevOps tools for Java developers! The VM is an Ubuntu image with Eclipse installed. It also has Team Explorer Everywhere and all the other software you need to kick the tires as a Java developer. The lab instructions are hosted in our Github repo.
The labs walk you through:
- Creating a free VSTS account (if you don’t already have one) for storing source, managing work items, automated builds, release management and more.
- Logging work items and using the Agile Portfolio Management functions, from a browser as well as from within Eclipse
- Importing some source code using Git
- Using Git Pull Requests with Eclipse and VSTS
- Creating an automated Continuous Integration (CI) build to build a Java website using VSTS’s cross-platform build agent
- Creating an automated Release Pipeline for deploying the site to Tomcat (using a custom extension from the VSTS Marketplace)
- Adding automated Selenium tests that run during the release pipeline to validate deployments
- Monitoring Java applications in production using Application Insights
We’ve also included a couple of Azure Resource Manager (ARM) templates that help you get the VM set up and running in Azure in around 15 minutes.
It’s never been easier to explore how great the Microsoft DevOps experience is for Java Developers! Take the VM out for a spin and run through the labs. You can log issues on the Github repo or mail firstname.lastname@example.org for assistance.