I’ll be straightforward at the start of this post: I firmly believe that the most important issue a company deals with is how it reconciles itself with technical debt. Period.
Now, here’s the real point of this post: Technical Debt is a Positive and Necessary Step in software engineering.
With the growing need to quickly release software and add value for customers, the trend towards continuous delivery is undeniable. At the same time, challenges exist in managing code quality within the software delivery pipeline. We will show how you can extend your existing Jenkins setup to orchestrate full Continuous Delivery with a focus on quality by leveraging the Jenkins Workflow plugin to create and manage your CD pipelines, and by using XL Test's aggregation, reporting, and qualification capabilities within your pipelines to understand and manage quality.
Previously the technologies Microsoft offered around Application Lifecycle Management (ALM) were, and in many cases still are, clunky. They also were highly predicated on you being a Microsoft shop, down to the hypervisor. Even so, their investments and publicized direction were to go even higher up the chain, into the DevOps framework. But it was not always clear how they were going to do it. Now it is, it is going to take the vision behind Visual Studio Online VSO and Azure to make the DevOps story play out.