GitLab GitLab 13.4 Release Product Kickoff, 13 Aug 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: GitLab 13.4 Kickoff - Release:Progressive Delivery

Description

GitLab 13.4 Kickoff - Release:Progressive Delivery

Planning issue - https://gitlab.com/gitlab-org/ci-cd/progressive_delivery/-/issues/8#note_372481144

A

Hi welcome to the uh 13.4 progressive delivery, kickoff video, my name is erica lincke and I'm a senior product manager of the progressive delivery group- and I have with me dimitri.

B

Hello, I'm dimitrixtra one of the product designers at gitlab for progressive delivery.

A

And today we're going to walk through what we have planned for the next milestone for 13.4.

A

um So, let's get started, you can follow what our planning issue it's under the progressive delivery project- and this is issue number eight um titled pd 13.4 planning issue.

A

So I'm going to go through um the highlights of what we're planning and we'll start with our top priority deliverables and the first one is add: support for canary weight, ingress annotation uh via api.

A

So the past few months we have been doing quite a bit of preparation in order to make advanced deployments more flexible. So the way that we're doing this is by giving you the ability to add annotations into your canary release, which will allow you to do from the beginning blue green deployments.

A

But you can also it'll be much more flexible in the future and the first one, one that we're introducing in order to achieve blue green deployments is weight, ingress annotations and for the first iteration we're going to allow this ability through an api which would let you to set the weight to 0 or 100 and then switch from blue to green.

A

The next, uh the next feature that I want to discuss is uh our top voted uh popular issue, which is moving features to core. So we're planning in the next milestone to move feature flags to core so that everyone can benefit from the I'm using feature flags at the moment it is under only premium license, and now it's going to be uh open source for everyone, so that everyone can benefit from future flags.

A

We're really excited to bring this to a much larger audience and to get a ton of feedback uh from your usage and hear what you think about the features um now. Moving on to dimitri.

B

All right, um the next issues allow for easier rollback from alerts from the alerts page.

B

This is going to make it easier for sres to take action on an alert, and this we're going to enable this through um making it easier to navigate to the environment, where you can see your role uh rollouts and, um if decided so, to roll back on any one of those.

A

Yeah great to meet you so just to emphasize. This is another activity that we've been working on for quite a few milestones, which is to give you more visibility of what's going on in the system, post deployment or during a deployment. So now uh on the alerts itself, if you see a problem, you can go directly to the environment and check it out and continue trying it. um The next feature is the backstage issue. So it's not one of our highlights. I'm going to skip it and let dimitri continue with our next features.

B

Yeah sure so the first one we're looking in here for our priority three issues is to display a default list when adding environments to a feature flight strategy. The problem currently is when you're inputting a environment you're presented with a little drop down without any default values available there to you. So it will always require an additional click or search query to display the environments for you to click on and configure your feature flags to with this improvement, we're going to make a small improvement that will immediately allow those values to be visible for you.

B

So you can click through without need to search through unless you need a specific environment which is not immediately shown.

A

Awesome and our final deliverable issue before we walk into uh search issues.

B

Yes, so this is a small improvement as well. uh We're gonna make a um a call out a callout ui element uh dismissible, and this is going to take.

B

This is going to persist across sessions so where this this callout is currently always shown or will continue to show even after being dismissed across sessions, it will now be able to persist across sessions, while you're already informed as a user.

A

Great, so we're going to try something different, this kickoff and talk a little bit about our research efforts. um So dmitry. Would you like to lead us there.

B

Yes, so this is pretty exciting for progress, delivery, um we're going to make jobs to be done, which is a certain framework of being able to figure out what exactly our jobs of our customers and users are across the progress delivery stage group are and how to make sure that we're delivering the most value we can across all those different needs and from our users um we're going to approach this through research and through existing research figure out what jobs to be done are there and then based on those jobs to be done?

B

We can further dive in and see our eight. How? How well are we doing for this one? How well are we doing for the other one and it will make um it will enable us basically to be more efficient in delivering value towards our users.

A

Yeah and I'd also like to jump in and request any volunteers that want to participate in our research to go ahead and contact us whether it's on this issue, which is for us to deliver issue number three. Let us know if you want to take part in this research effort and last but not least,.

B

Yes, a small update on the a b testing research for problem validation. um This research is well underway. All interviews have been concluded inside synthesis is currently being done so from all the interviews that we've done um we're now looking through what has been said and how that relates to each other's what what patterns are forming and from that, and it is nice if you scroll a little bit down, there's a task list where it can be seen what is still up ahead.

B

But with those insights we'll do white boarding sessions, we'll do some some ideation and eventually create a holistic view of what a b testing is going to be within the progressive delivery stage group of git lab and how that will eventually deliver the most value to our customers. As we can.

A

Yeah, we're super excited about going ahead and diving into an a b testing solution for everyone, we're really psyched about the fact that we can expand our current uh feature: flag functionality, even more and even open this up for additional personas and internal functionality and give our customers great value and see everything across the entire pipelines and and really help them make the best decisions on. What's the right, a or b way to go, so we're really really really excited.

A

And again um I invite anyone who wants to give us feedback or comments or volunteer uh to participate in this uh research again. um So that's all we have planned for 13.4 right now. uh We're really excited about uh all this value that we're going to be deliver delivering and we're really looking forward for a really really great release.

A

um So thank you again and uh see you next.

A