Deploy quicker and safer with new greenlighting capabilities in VSTS

Sign in to queue

Description

Greenlighting is a new feature in Visual Studio Team Services. Greenlighting is using monitoring and automated systems to complement your release approval gates. This session covers why you need greenlighting in your release pipeline, and how to set up greenlighting.


Product info: www.visualstudio.com/team-services/
Learn more: docs.microsoft.com/en-us/vsts/index#pivot=services

Day:

0

Session Type:

On-demand

Code:

T181

Embed

Download

Download this episode

Download captions

The Discussion

  • User profile image
    Dave Williams

    This feature has such promise...but man talk about a clunky poorly thought out experience. I'm left scratching my head....where is the view that shows the end-2-end workflow that shows you 1) Deployed the canary build and monitoring showed (after 5 minutes it failed), 2) A new build was built and deployed that had the feature flag set to false (right this value is stored in GIT, one source of truth right???), 2) The Feature flag build (with the value set to false) was deployed and monitoring returned to nominal. The experience you showed has all of the pieces but now of the glue that EASILY summarizes the overall historical view of what happened and most importantly WHY it happened.

    Something along the lines of:
    DEPLOY BUILD 123 TO CANARY-->MONITORING FAILED-->NEW BUILD 124 (WITH DISABLED FF) DEPLOYED TO CANARY -->Montoring Error Rates nominal

    Hopefully, you can provide a nice, CLEAN, END2END view of the process...this just reeks of being an MVP (minimum viable product) and not being an MLP (minimum LOVEABLE product).

    Keep up the great work.

Add Your 2 Cents