 Hello, my name is Cesar Cvedro. I'm a technical marketing manager at GitLab. In this segment of the presentation, I'm going to be covering a new capability called Automatic Rollback in case of failure. This was introduced in GitLab 13.7. It's basically the automatic rollback in case a critical alert is detected. So this is done by the GitLab platform. And what gets Rollback is the most recent, successful deployment. It's selected and redeployed. So why does it matter for customers and prospects? This capability allows SREs and operators to set up critical alerts in production so that when those alerts are triggered in a problematic deployment, let's say is a threshold for the amount of memory that your application is using. GitLab will roll it back to the most recent successful deployment. This automation eases the described workflow above for SREs and operators. It also serves like a second line of defense for code updates that pass CI tests and are deployed to production. Here are some resources to learn more about this specific capability. There's a link for the documentation and issue. And I will paste a link to the demo once it's ready. Some things to follow. There is a link to the progressive delivery direction that talks about where we're heading with these type of capabilities. And also the post-deployment monitoring epic that contains a list of all the related work items that are within progressive delivery and include this capability. And capabilities like this one too. Things to keep in mind, the rollback is skipped if a deployment is running when the alert is detected. And also a rollback can happen only once in three minutes. If there are multiple alerts detected at once, only one rollback is performed. Okay, now let's move on to the demo. So here you see a project called Provanager Spring. And I'm logged on as Devin. He is a DevOps engineer. And first thing we need to do is we need to enable automatic deployment rollbacks. So as you can see here, it's already enabled. And what this will do is if there's a critical alert triggered, the rollback, there will be an automatic rollback done by the platform to the last successful deployment. So that's already set. Well, one more thing I want to show you is what I'm going to be deploying by starting this pipeline in a minute. Introduces some changes. And the changes are here. In the index HTML file, the headings of the table are all in capital letters. And there's also a misspelling here. So those will be the changes that are in those are the changes in master and the ones that I will be pushing by creating or running a new pipeline. So we go here. And as you can see, there's been two successful deployments earlier today. Please ignore this cancel once I started them by accident. And now we're going to run a pipeline. And while that's running, let's go to the operations environment, actually metrics and create an alert. So let's create an alert here. Let's make sure that this is the total memory usage. And let's make sure to create an alert that will be triggered. So let's make let's say the average is 2.61. So and right now it's 2.45. So let's make it to two right there. Okay, so it detected that it's below the threshold. So it should fire an alert. It hasn't fired yet. Let's see. Okay, so the pipeline is running. Okay, so now that the pipeline has completed, the deployment has taken place. And let's see if the alerts has come in. Yet there's a critical alert that already happened a few minutes ago. So let's so let's see if that triggered a new deployment. So let's go to environments. Now notice here that the job that was executed is actually not the job in the pipeline. So if you look at the pipeline, let's go to the pipeline. So the pipeline that executed here, seven minutes ago, it finished. It has an automatic deployment to production. This is not a manual step. Okay. Now what I would like you to notice here is that this was updated eight minutes ago. Right? So it was updated after this pipeline completed, which means that the the critical alert triggered an automatic rollback and also noticed that the job is a job that does not belong to the pipeline that we just ran. Right? This is in fact, let's go there. And this job is actually a job of the last successful the last successful pipeline. So the automatic rollback has taken place. Yes. So the latest successful deployment included the edit and the new product are have a purple background. But if you notice the titles do not have they're not in capital letters like we we saw earlier, which is what we pushed in the pipeline that actually was automatically rolled back. That's all I have. Thank you very much.