GitLab Delivery Team Fast Boot, 30 Apr 2019

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Delivery Fast Boot: Robert task Day 1 summary

Description

Delivery team fast boot Day 1, Robert recaps the task for finding the commit with a green build which is a starting point for building a deployment package.

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

A

Doing me the monitor on right.

A

So what was your task? Robert I was.

B

Thinking emerging, Westerbeck, Mary started on to find a green, build on master for all of our projects. Mm-Hmm then trigger a build of that emergence or not that I've adapted it to work on any branch we get it so, for example, if we wanted to find the last passing build of eleven seven staple first, it finds a pretty e. It found one like it's the urchins and let's proceed.

B

Taking a little longer.

A

No stress no stir.

A

So why are we doing this? Why.

B

Are we doing this, so we can trigger a build, a specific point in time from a specific shot. That we know is good at n-nothing mmm-hmm. No, you just don't get an argument. It'll do it for master.

B

C

A

Been a while, since we had a green master, so.

B

It might not even find one.

C

B

Is on get Lancome and then it looks to verify that the same passing the shot has been as been nice. That's.

C

Really helpful so.

B

The source of truth for our builds is calm. Then the source of truth for our tagging is death. So this.

C

Is really nice because we need this for all the deploy as well. I had the logic to find the latest green to me, but I wasn't looking all dead and these auto deploy branches.

B

Are protected so they're here about that yeah use this. This is logic, skarbek build and I just expanded it to work on any rep. That's great.

D

D

B

Weird thing to note that just came out from this: we have a different workers version on C, E and E for eleven seven I, don't know what happened there.

B

Maybe we bumped it for something that was specific to us. I, don't know that.

A

Is a good find.

D

A

Probably related yeah.

C

First version for that security release, so yeah yeah yeah they bumped it in for that. So alright.

A

C

Green mastering now see. That's really, that's really bad, because that security really should have gone over to CD as well. Well,.

A

I think that security release was related to e feature only and that's probably the reason why there is a difference, although I'm not too pleased that we actually have a different version between the two, because that's gonna create confusion.

A

Well, single codebase, someone will say all right, Wow awesome. This.

C

Is actually really also did it change? Did you I think the other deploy stuff is also.

B

Actually, almost certainly all broken because I renamed it from.

C

Same but the tests yeah okay, but this is great- that's actually.

A

That's quite a a lot of progress. I.

B

Mean building on scarring stuff from last week, right.

A

D

Some have been working on for over a month is just a vacation and Iceland. You.

A

Need to give some credit to yourself, you.

D

Were on vacation.

A

For two week come on scar, back awesome, yeah.

C

A