GitLab Release Group, 26 Jan 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Resource Group Speed-Run

Description

Speed run of the Resource-Group setup and functionality
https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/36621#note_274561578

A

Hi, my name is Erica Lewinsky and I'm the product manager for the progressive delivery group for the release stage at gitlab today, I want to walk through something that we just delivered in release. Oh that's: I've been called limit pipeline job from currency by resource group, so sometimes a user might want to limit the resources that can be deployed to at any given time or even a job within a specific deployment so that there's no destructive activity done for that resource group.

A

So a resource group can maybe be a physical device, a mobile phone or something similar that we can only allow one deployment to happen at any given time. So we introduced a new format of called resource group that you define inside the collab CI mo file and that will actively limit that job in the pipeline. So let's, let's get to it. So imagine we have a very, very simple pipeline.

A

Which only has two jobs test and deploy and we'll take a look at the good, lepsy IMO file and then add another job called deploy to which will use the same resource group, and we will make sure that only one of them can be deployed to at any given time.

A

So for that we're going to open the web IDE.

A

And take a look at our piano file, so we can see our two stages tests and deploy and each one of them does something and that's what we saw in the pipeline and now I want to add another deploy, job which belongs to the same stage. But now I'm. Introducing this new name called resource group iOS resource group. Ios iOS is just here for an example for you to imagine it's the pointer, a mobile phone, but it can be named anything that you want.

A

You can also have multiple resource groups deploying to in a specific job. So if, for example, you have several phones, each one of them can be a separate resource group, so I'm gonna go ahead and commit this change to get left, see IMO file and see what our pipeline looks like now.

A

A

As we can see, the pipeline is running. Let's take a look at it.

A

So now you can see we have a test job and a deploy. Job, which is has the two different jobs inside in parallel, deploy one and two point two, and you can see this new icon. That tells you that it's waiting for resource so as long as the first deploy job is not finished, the second job will not run you.

A

A

Now the job has passed, and now the other job that was waiting for resource can now run.

A

A

I can even try to retry the previous job and we'll see that when I do that now, this job is waiting for a resource.

A

And you saw that once this is complete, the other job is free to run. So this is how simple it is to define a resource group within your left, CI Yama file. We think this is going to be a very powerful feature and help you with your future deployments. We would love to get your feedback and comments on this as always either on the issue of themselves or by you know only me directly to Olga Lewinsky at gitlab comm. Thank you.