GitLab GitLab 13.6 Release Kick-Off, 18 Oct 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: GitLab 13.6 Kickoff - Release:Progressive Delivery

Description

GitLab 13.6 Kickoff - Release:Progressive Delivery

Planning issue: https://gitlab.com/gitlab-org/ci-cd/progressive_delivery/-/issues/22

A

Hi, my name is erica lewinsky and I'm the senior product manager for the progressive delivery group under the release stage here at gitlab today, I want to walk through some of the really exciting stuff that we have planned for the 13.6 milestone. So let's get started.

A

So the first issue um that I want to talk about is this issue. um It is 26378 and this basically is going to migrate sql um in order to ensure that auto deploy under auto devops still works after this upgrade that's planned for november 13th.

A

uh So we're going to try to work uh everything under the hood so that everything still works after that date.

A

The next issue that we're going to talk about is one that is highly popular and it's a break off off of epic for a way to clean up unused environments, mainly review apps, but not only so. um In a 12.8, we introduced a auto expiry keyword that allows you to set an expiry date for um environments, uh but that was only uh initiated when there was an actual deployment in this issue which is set. Auto. Stop environment expire me when it. When an environment is created.

A

um This will actually do the following. So you're gonna we're still using the auto stop in keyword, but now it's gonna do one of two. So um either this is going to be counted from the day the environment is created or from when the environment was deployed. So now, even if there's no deployment, there's still going to be an auto expiry.

A

But if there is a deployment, the counter will be reset um and then the expiry will only be from the from the date that an environment was deployed so really excited to make everyone's life a little bit easier in that sense and make sure that there's an automatic way to delete unused environments.

A

Our next issue is pending on the completion of of its parent, but what we're really trying to do is make it easier to set traffic or canary on the play boards. um So in the previous milestone, we started working on this for an api base and now we're trying to do it in the ui. So what this will look like is that, on your deploy board, you'll have this uh stable and canary option, which will let you set one of them either.

A

One of them and the other one would adjust accordingly to to reach 100 so that you can make sure that you're setting the weights for what you want on your new deployment versus what you have in your stable production environment, and you can gradually um change the the rollout of your different pods.

A

So we're really excited about also the visualization of this, uh but also, as I mentioned, it's going to be supported both in api and in the ui.

A

This will also be a really nice way to achieve blue green, so you can do it with zero percent or 100 percent, and just really excited to get this. uh This rolling a really nice uh continuation that we have is auto deployed to ec2. So in the past few milestones, we've added support for autodeploy for ecs and faragate, and the last milestone. We provided a template, a gitlab, ciaml template and you can take and just deploy to ec2.

A

This will connect it to the auto devops flow and introduce the auto deploy to ec2 template.

A

um Yeah, so next we have a bug that uh we're also excited to to. Finally get around to fixing is a review app created from child pipeline does not show up in merger quest, so a few milestones ago. The verify team did some really amazing work and introduced the concept of parent child pipeline. uh The issue there is that the review app is still connected to the parent pipeline in the yaml file, and that's why it's not showing the child review app and so we're gonna fix that in this release,.

A

Next up, we have uh forward deployments which will warn users on retry, so this is just another way that we want to improve the workflow.

A

um What this is going to do is in case someone tries to retry a pipeline when there's a forward deployment setting we're going to warn you that you're about to retry a job that failed by forward deployment, and this may override uh the environment with older source codes. So this is a another measure for precaution to make sure that you indeed want to overwrite to an older deployment.

A

So next we have added documentation for cicd, using gitlab ci and amazon aws s3 we're actually going to introduce some docker images that you can use in order to deploy to s3 and document that, so it will be easier to follow and use in your pipelines.

A

And, last but not least, we have add the ability to copy feature flag user lists uh to clipboard, and what we want to do here is just make your life easier when you want to re use user lists in between lists.

A

So now you actually need to add each user one by one which makes it really hard to reuse, so we're going to make it easier to copy and paste users from one list to another. Making making this just so much more convenient, there's some more small issues that I'm not going to go and highlight, but if you would like to read them through, you can check this out on the progressive delivery project under issue.

A

Number 22, pd 13.6 planning issue super excited for this milestone and can't wait to hear your feedback and comments on the issues, and I will see you next time.

A