Interview with Munil Shah (Quality)

Sign in to queue

The Discussion

  • User profile image
    David L

    Could you have a deeper dive on the L2 test and the new L2 test framework? Very interesting.

  • User profile image
    Niner551388

    Again, thanks for a great talk that provides a lot of insight.

  • User profile image
    Donovan

    Again, thanks for a great talk that provides a lot of insight.

    Thanks for watching.

  • User profile image
    Donovan

    Could you have a deeper dive on the L2 test and the new L2 test framework? Very interesting.

    I will work with @munils to have him back on the show again.

  • User profile image
    fleed

    Thank you, Donovan, for bringing such a great series!

    Can you please dive into the details of build and release definitions? L1 tests and the containerized host would also be a great topic.

    I'm trying to bring a similar transformation in my small SW team, and I'd like to get as much as possible from your experience

     
  • User profile image
    James

    Very interesting talk. I'd like to know more about how Release Management is used to facilitate hotfix builds going into the pipeline, when further down the pipe you might already have another release still rolling out, how do you mange that scenario? How do you mange the rolling back of the binaries in the event a roll back is required, is this automated also in RM or is this manual? Great series, always interested to here how the VSTS engineering team manage their processes.

  • User profile image
    munils

    @James hotfix rollout depends on the severity. For sev 2 and 3s (i.e. lower severity), they go through the same deployment ring model. For Sev1s, we deploy through ring 0 and then can skip to impacted scale unit if it is isolated to a particularly scale unit. Otherwise it also follows normal ring model. For Sev0 (highest severity), we deploy as fast as possible to alleviate the problem. If another release is already in the pipeline, then the hofix may take a priority as explained here. We need to craft different versions of hotfixes depending on where particular scale units are. Regarding roll back, yes it is automated. After updating the binaries, we check a set of health monitors. Based on specific thresholds, the binaries are rolled back if things don't look right. Hope this helps.  

Add Your 2 Cents