How do I roll-back a VSTS extension when I am using a CI/CD pipeline?

A few days ago, 2 to be exact, we experienced a critical issue in production when we released a public extension update. It reminded me of Brian’s post A Rough Patch. Similarly, the user experience was not good. Reality set in. We must think about roll back when we design our CI/CD pipelines. Let’s explore…

4

Our journey to WhiteSource and OSS security, licensing and quality checking

This is the third, and final, article in the WhiteSource series for managing open source usage and security in your CI/CD pipeline. If you haven’t viewed the previous articles, I recommend you take a moment to review them now: Manage your open source usage and security in your pipeline Manage your open source usage and…

0

VSTS Bot is now in Preview

I am happy to announce that starting from today I will be available as preview and the code is now available in the master branch: https://github.com/ALM-Rangers/VSTS-Bot Also I got my own website right here: https://team-services-bot.azurewebsites.net/. Thanks to the ALM | DevOps  Ranger community, I can now help you with Listing the build definitions and queue…

8

Azure Function – Provisioning and configuring our Azure Function infrastructure

In our earlier article, Azure Functions – Prepare for continuous delivery, we began our series of blog posts on using Azure Function with Visual Studio 2017. We continue the automation of the creation and update of our Azure infrastructure, also known as provisioning. It’s important that we can recreate and configure our infrastructure in a…

0

Azure Functions – Prepare for continuous delivery

As part of our research of using Feature Flags with VSTS extensions, we exposed our secure VSTS token based solution, implemented with Azure Functions to: Generate a hash Key by server-side To call the REST API of LaunchDarkly We’re dogfooding our own research outcome! We’re implementing the Azure Functions, backed by a CI/CD pipeline. In…

1

Our journey of a continuous transformation to a DevOps culture

In 2015, the ALM Rangers moved from a traditional organization to self-organizing teams and embraced a DevOps culture. We started an article, or is it a journal, that captures the process we used, the results we observed, and how the Rangers reacted to the transition. You can find the latest version here. It should come…

0

Building VSTS Extensions with feature flags – Part 3

We shared possible scenarios for using feature flags in part 1 of our research. Part 2 focused on securing data sent to LaunchDarkly using the Azure Function. We continue with the call of the LaunchDarkly Rest API from VSTS extensions. You may recall, that we intentionally deferred the scenario in which the user decides which…

0

How to integrate Application Insights monitoring in your VSTS extension

Monitoring your team services extension is an important DevOps practice. In this article we’ll demonstrate how to integrate Application Insights telemetry in your extension by using our new Telemetry Client for Team Services extension. Prerequisite – You need an Azure subscription and an Application Insights resource. Step 1: Required modules Reference two npm modules dependencies…

2

How to create or upgrade your VSTS extension in 4 steps

My contribution to the Yeoman generator for the VSTS extension project helped me improve the way we create extensions. Starting from the way we structure the extension files, the JavaScript minification, how we generate and publish the extension package and down to monitoring the extension usage. The goal of this post is to walk you…

0

Setup a CI/CD pipeline with package management for your VSTS extension

In recent posts we covered our CI/CD pipelines for the Yeoman generator package, for simple extensions, and for extension with unit testing and code coverage. We continue by exploring our Roll-up Board extension pipeline, which pulls a shared package from the Package Management in Team Services. These CI/CD pipeline posts are based on our Applying…

0