GitLab Progressive Delivery, 14 Sep 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: GitLab 13.5 Kickoff - Release:Progressive Delivery

Description

Planning issue: https://gitlab.com/gitlab-org/ci-cd/progressive_delivery/-/issues/13#note_391349561

A

Hi, my name is enrico 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 content that we have planned for the 13.5 release, so I'm going to go ahead and share my screen and let's get started so as always. If you want to walk through and see what we have planned, you can check out the issue on the progressive delivery group project issue number 13..

A

It's called pd 13.5 planning issue and I'm going to scroll down to arts and the verbals. So um one of the first things that we're going to be working on is a template for deploying to aws cc2.

A

uh Previously we uh developed and delivered the option to deploy to ecs into fairgate and even connected it to auto devops, and this is again the same systematic uh way, we're going to provide a full gitlab ciemo file that does deployment to ec2 and in the next release, or so we will also connect this to autodevops.

A

So this expand the the targets, employment targets that you can deploy to using gitlab.

A

The next issue that I'm really really excited to talk about is automatic rollback in case of failure, so we um in the previous milestone, we delivered the option to see to view alerts on the environments page and this. What this does is in case there's a critical alert that you can find on your deployment.

A

This will do an automatic pullback, so there's going to be a new setting that can be selected whether or not you want to choose this option to automatically go back in case of an error. But if there's a critical error- and you select this option, um the deployment will roll back to the previously last successful deployment.

A

So this is really exciting as we're introducing more opportunities for automation on your pipelines and making sure that when something goes wrong, you have an easy way to roll back and make sure that you don't have a lot of interference or problems in your current production.

A

So really really excited excited to hear any feedback that you have on this issue as well.

A

The next issue that I want to talk about is small one: create job, stop ecs review apps. So, as I mentioned before, we added that option to deploy to pcs using auto devops. However, we did not have an auto stop option for those review apps. So this is what we're adding in this milestone um and another. The next one is api support for uh forward deployment enabled so in a few milestones ago, we added the option to make sure that you are always on the current deployments.

A

It skips outdated deployments and make sure that you're on the latest one- and this is supported via setting in the ui, and we had a request here to add additional support through api, and this is what we're going to do here on this issue, as I excited to be enabling this for other use cases also doing it only through the ui makes you go through each project and select that one by one api support, allows you to create a script and potentially use this on that or many at one time and last but not least, we're adding documentation for cicd using github ci to amazon s3.

A

So this is not yet providing an s3 template, but it is a addition to our documentation to explain how you can deploy two s3. So it's one step before we actually add the template, which is planned. So I'm really really excited to see this uh release be delivered. I'm excited to hear any feedback that you have. um As always, you can either ping me on the issues themselves or contact me at logalowinski, gitlab.com uh and I'll see you in the next.