Post 2- Value Stream Mapping for ALM Ranger’s VSTS Extensions Work Stream

In my last blog post, I wrote about benefits of Value Stream Mapping (VSM) in the realm of software development. I also wrote about how we, the ALM | DevOps Rangers, plan to use it in our VSTS Extensions work stream. Our first target was to produce an “AS-IS” Value Stream Map. For this, our…

0

How to analyze your open source project with SonarCloud and VSTS

Among the code analysis tools, there is SonarQube which I think no longer needs introductions and which has very good tools to integrate in your DevOps pipelines. However, setting up a SonarQube infrastructure requires servers and resources and therefore time and maintenance costs. For more documentation read ours posts:  How install SonaQube with ARM Template…

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

Azure Functions – CI / CD DevOps Pipeline

In earlier parts of our Function Azure blog post series, we outlined the implementation of different artifacts of our research project on communication between the VSTS and LaunchDarkly with the Azure Function extensions. In this one we will present how we have implemented continuous integration and deployment of our Azure Functions in Azure using Visual…

1

Resolution for WhiteSource “Unhandled: error is not defined” and “where’s my project” issues in our CI/CD pipelines

One of the pipeline we’re fine-tuning as outlined in the manage your open source usage and security as reported by your CI/CD pipeline post was recently blocked with two issues. Issue 1 – “Unhandled: error is not defined” Last week the build started to fail with the “Unhandled: error is not defined” issue, as shown. …

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

Building VSTS Extensions with feature flags – Part 2

In Building VSTS Extensions with feature flags we started a discussion about feature flags and how we’re using LaunchDarkly to eliminate risk and deliver value. We closed with a brief mention that we’re trying to find a way to exchange a more secure user key as part of the communication between our extensions and the…

0

A really COOL feature we noticed on VSTS – New Release Definition Editor

The feature was introduced in New Release Definition Editor in Team Services. It’s therefore not really a new, but a cool feature that we explored and fell in with. Looking back – this is how one of our pipelines look when viewed in the current (old) release editor. Looking forward – this is how the…


Building VSTS Extensions with feature flags

We started talking about features flags (or features toggles) in our Software Development with Feature Toggles MSDN Magazine article. Today, with the increasing deployments of our extensions, and with a view to improving the user experience and our DevOps processes, we embarked on a research project to investigate the feasibility of using LaunchDarkly to eliminate…

0