GitLab Support Operations, 7 Feb 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Support Ops - Repo Setup - Mirroring when source doesn't exist

Description

Jason Colyer, Support Operations Manager, takes us through setting up a repo on gitlab.com and having it mirror to an ops instance. This is specifically for when the source project (ie the one on gitlab.com) does not exist.

A

Greetings all names, jason, collier support operations manager here at get lab, and today I'm going to cover um setting up a project in gitlab.com and having it mirrored to our ops instance and everything that's required here. So in this particular case we have the project zendesk automations, that exists on the ops instance, but you can see over here on gitlab.com.

A

It does not exist. So the first thing we're going to do is create the project. Now, since we're uh we're, gonna do plank pro blank projects, and this is in regards to automations.

A

I wanted to be private, we don't need any of that so create project.

A

Now, with that done, we have our project, but we need to go ahead and get it to pull this initial code now to uh to get it to pull the initial code. We're gonna have to set up some uh some tokens, some access tokens. So what we're gonna want to do is set up the access tokens on the source or on the sorry, the target. So we're going to go to settings access tokens.

A

What we would do is give it a name so something like mirroring and then we'll go ahead and maintain her, and we can just click all of those, because it's going to show the token I'm not actually going to save it on the recording.

A

But uh once you're done with that, you click the blue, save and then you'll have this nice new token ready to go now. What we would want to do is do the same thing on the target um when we don't actually need it on the source here. So there's some other settings. We want to go ahead and tweak while we're here. So let's go to repository.

A

Protected branches, we can go ahead and remove it on the target, because we're going to be mirroring from this will just prevent it from having some errors there, we'll also want to edit the ci cd we're going to go to our variables and we're going to add a new one run underscore job and on the ops instance here it is set to true and what we'll do is set the same thing up on our gitlab.com instance.

A

So add variable, run job, and this one is false because we're not going to be running them over here, all right. So with that in place, we now need to go ahead and set up the mirroring. So let's do repository.

A

Mirroring what we're going to do is over here we're going to grab that get url. We want the https version, we're going to do a username, we're pulling from it and we need to give it the access token we generated, and we we don't need to worry about all this now, since we're just pulling the initial stuff.

A

We'll go ahead and make sure that it's updating and if we go to the project, there's our code, so we've now got that set up, so we can go back to our repository mirroring and we can get rid of this pool mirror. We don't need it anymore now. What we do need to set up is for the get lab.com instance to mirror to push updates over here over to the options, and so once again we're going to set this up at this time.

A

We are pushing make sure to give it that access token from the target, and this time mirror only protected branches. We only wanted to do the main default master or whatever branch.

A

So with those set up. We now need to edit our ci cd, so we're going to go to our ci yaml here and we want to edit this now. Essentially, what we want to do is have the from zendesk job. The compare job and the sync job only run over here on the ops instance, but the from repo job can run either way. So, first we're gonna set up an empty rules bracket for from repo because it can just run anytime.

A

It's not a big deal, but for the from zendesk one we're going to set up rules and we're going to do if run job. True now, this will essentially say to only run this job. If that variable run, job is true, which it is not on the com instance, but it is on the ops instance. Now we're going to go ahead and add that.

A

Add that to our compare and our sync jobs, there we go, and that should be all we need there, but um worst case scenario. We can always like you know edit this as needed, so we'll do a commit, adjusting ci rules or mirroring and we'll create a new merge request, uh the benefit of doing it. This way is we are going to be able to see if it's working correctly, uh we'll add our labels automations.

A

We're doing it our priority is normal. Our milestone is this deployment. We're gonna go ahead and assign it to myself and we'll squash commits.

A

Now we can see how it's already said: it's detached pipeline has failed. So if we look, you can tell me, okay must have typoed a little bit on that uh that, mr, so let's look at our changes.

A

From zendesk rules, rules, rules.

A

Looks correct to me.

A

But when in doubt we can look at a pre-established one and see if we've uh typoed something there. So we know this one's working in macros and I can see how I clean things up a lot on this one. So I feel like that's something we can go ahead and do here so we'll open in web ide.

A

And I'm just going to do that to clean it up and I'll call it cleanup.

A

Okay, so we can refresh this there we go yeah. I probably had some bad spacing in that original one. The that one looks much better.

A

All right get rid of those. We can see how the pipeline should complete and what we want to do is check that it only ran the from repo. That's correct. We don't run running everything else here.

A

Cool, so what I'll do is mark this as completed I'll, approve it and we'll merge it.

A

Now, while that does that, let's uh go to our settings real, quick, there's some things we want to adjust here so um request approvals- you want to get rid of these, save it like that, we're going to add an approval rule we're going to call it support operations.

A

We only care about the main branch, and what we're going to do here is.

A

Add myself and dan and just for a second we'll, add gl support bots.

A

Now the reason we're not writing the rest of operations is. This is a us federal one, so we only want the us federal ones who can maintain the actual code doing it. So, with that set up, we should be in a good place. We would want to normally set up like the merge request settings. um Some things we would normally want to do here is require that pipelines must succeed.

A

All discussions must be set and then we'd want to set our default, merge request, but we'll you know our template, but we'll do that at a later time.

A

So uh with that all done, let's go ahead and check the status of our mirror.

A

We will go to mirroring says it just push now so, let's refresh over here, and we should see that new ci update and there we go and that's all there really is to it with that. It's set up it's good to go, update your documentation and you're ready to continue hope. You found this educational look forward to seeing you in the next video.