GitLab Delivery Team Fast Boot, 30 Apr 2019

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Delivery Fast Boot: Day 4 run the process - attempt 2

Description

Run 2 of the process and addressing the challenges as we go along.

The issues listing the work done are contained in epic https://gitlab.com/groups/gitlab-org/release/-/epics/17

A

All right, I think we're ready now. Yes, please check that off. We confirm that's working now.

B

A

Right so, let's see is this is what we wanted to do so create a temporary branch that is already created and it should be synched. Now that the mirroring is working.

A

Do those branches need to be protected.

A

C

C

A

That temporary branch was created from a random, commit you merged already the Omnibus get up into that wrap branch, jar.

A

Then we did I added in release tools, I added this version of auto deploy branch, I created pick into label applied, and we already I think start from point two. What does that actually mean.

C

A

Special Branch: let's see.

C

C

We want to use the variable, we want to start off the chair thing. So cherry pick underscore Auto underscore employee, underscore branch carry Minister schedule chair.

A

Your things won't work, but it's not though okay well, the will.

C

Pad is it's a branch under schedule.

A

A

All right do we need, can you go back to the pipeline.

A

C

We need all of these things.

A

A

Oh, oh, that would.

B

A

They not going to pass know.

B

B

A

No! No! No! No! No! All right! That's fine! Yeah! Exactly.

B

A

All right, Robert, you're, updating the contact right.

A

Can you just run okay that works as well? I guess.

B

No I meant, like maybe yeah, it doesn't matter.

A

Just start to bake lunch partner again.

A

Yeah, that's exactly what I meant.

A

B

A

C

For a I, don't think the polls I.

A

It does what it's waiting for something it pause mean stuff really well, there's a different icon for soccer right. There yeah! No, it's like an information point.

A

C

So this is cherry picking this DMR's on to to give up seed and he nd into the heart of delivery and then doing the verge. Oh then, there's you're relying on the word. We're kicking it where's, Trina. Okay, then you'll kick off. The merge strains, be a trigger, yes, be.

A

B

C

And that's it. We are relying on the existing.

B

C

This movie just mirroring.

A

C

Yes, no wasn't.

B

A

A pit stop it's a good.

C

Watch failed, it looks.

A

Like something.

B

C

It's a century event, so.

A

A

I spend chairs.

C

If we want to do this again, will it fail because of what being able to pick we.

A

Need to re-emerge.

C

To show the Ugandan potent so we'll just continue right.

B

A

A

Yorick, we need to turn out the light for now Oh see now the the glare is pretty big Thanks just for now take three.

A

All right, could you do you have this previous job in a separate app? Can you open it.

A

A

Go to one of the merger quests.

A

Well, the label is no longer there nice all right. Well, that's good! That worked already 4 1 1 0 ee. That's fine!.

A

C

Say something else actually do ya, say something else, but the thing is: is that at this time we don't know what it's gonna go into, because we don't have a passing I mean it is sort of correct. It goes into the latest auto deploy.

C

B

A

B

Didn't want to trigger.

C

Anything we didn't want to trigger a seed.

C

A

Why wait why? Why are we bailing sure there is nothing to build, but that is assuming there is nothing to pick and see any, but we have omnibus as well.

A

Nothing is big there, but our.

B

Change is getting into the other branch someone.

A

Can merge something in the auto deploy branch if it's necessary to fix yeah yeah.

C

Maybe we should figure emerged train every time. This job runs yeah.

C

A

Merge string only to see anything.

A

But why did you build failed? Like that's? Why I understand you purposely.

C

Bailed out use a raise, but.

A

My point is yes: there there might be nut. That's the end of this job, we're only doing picking if nothing picked. It.

C

But it shouldn't fail. That's the filling the issue: yeah, just exit, zero right, yeah, exactly.

C

A

Reason for this is because you might have a change in omnibus that is required for something to run whatever it is, so you can still have the same, shall ve built, but in a different costume, but.

C

This this job, this job is not the tagging no.

A

C

For this job, I think, if we only care about, kill, em, CGD and I, think.

A

We'll eventually want.

C

To pick tomorrow,.

A

Omnibus yeah, and not only omnibus, all satellite stuff, yeah.

C

For now, I think they should just exit zero I agree.

B

If there's nothing.

C

C

A

It is, we cannot have it fail. Yeah.

C

A

We can, but it's not necessary all right. Well, that's at least simple enough courtesy of Robert superfast, typing I.

A

B

A

C

For testing purposes right now we no longer I had those things available to us.

C

I sort of think that maybe this should always trigger the merge strain. Even if there's nothing to pick and the reason for.

A

C

Like what, if what.

A

If the trigger fails or something in the middle and they try.

C

It and then the picks have already done, and then you're not going to trigger the merge strain. So I would say like the worst case right is that the merge strain will have nothing to do. Yeah.

A

It will clone to expend some cycles.

C

But do nothing I think you want to be able to retry this job together.

B

And I agree and even if the picks.

C

Were done but something else failed to them. Yeah.

A

Yeah yeah I, agree may as well real.

B

Quick chill enough cool been buggin yeah like if you wanted to leave this conditional and everything.

A

Th, where you twit- oh, that is cool, that's.

C

Nice, that's.

B

A

Left, you don't have a lot of plugins.

A

You have your dot piles, yeah they're on.

A

Github I, one of them are, we still recording. Yes,.

A

A

A

Right attempt number fear four.

A

Three three.

B

Languages mixing three languages.

A

A

B

A

You can you, can you go back to the merge of one of the merge requests that we opened.

B

A

So scroll all the way back down to the message. What should we say here actually automatically cherry-pick thing to auto deploy run on this one yeah yeah.

B

A

Is yeah I, don't know? Well, first, the branches.

C

Merged not into one one stable its merged into because.

A

This is using the prep branches right, yeah.

C

A

That will need two channels, just.

B

Say automatically.

C

Picks into the auto deploy branch.

B

A

Ended there for this I have another update.

C

When it gets yeah.

A

What we discuss that we are going to be adding a messages where okay, this is now deployed to whatever.

C

I, don't know like weather might also be useful to give them the URL to the bird stream after it's been taped in.

A

Case no clue what it is, that's the problem and they shouldn't, because this is our work around because of two code bases.

B

A

All right, what does the pipeline see.

A

Peeking all right.

B

A

A

A

A

B

A

Missing now it's missing it missing a variable to actually run a merge, train natural.

B

Killed it now, it's.

A

A

Yeah, oh no! Sorry! It's the other one right, Oh.

B

A

Alright, so we are missing that.

B

A

That's a bit odd, but.

C

A

Checking for existence in under yeah.

C

A

All right next, one.