Updates from the DevOps VSTS Bot

Dear community, I want to inform you for my upcoming update, which will be deployed on February 10, 2018. Update has rolled out, as of 9:00 AM CET. Encryption of sensitive information I have made sure that I only save personal information, that is needed to help us with your Visual Studio Team Services (VSTS) tasks. That resulted…

1

Value Stream Mapping for our VSTS Extensions

We the ALM | DevOps Rangers are a bunch of volunteers brought together by our enthusiasm of Microsoft’s ALM and DevOps technologies. Our mandate is to provide practical guidance, experience and gap-filling solutions to the developer community. Creating VSTS Extensions is part of our gap-filling solution. Currently, there are about 12 active VSTS Extensions created…

0

Roll-Up Board widget extension supports feature flags

We shared our research of the implementation of the feature flags, using LaunchDarkly, with our VSTS extensions in a series of blog posts: Phase the features of your application with feature flags Building VSTS Extensions with feature flags : Part 1, Part 2, and Part 3 Azure Functions : Prepare for continuous delivery, Provisioning and…

0

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