GitLab Delivery Team Fast Boot, 30 Apr 2019

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Delivery Fast Boot: Mid week confusion

Description

Delivery team fast boot Day 3: Updating version files, what gets triggered where and much more in this conversation. Definitely can be called the mid-week blues!

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

A

So does the version file and give that need to be updated before we kick off the on. You must my plate. I.

B

Thought he does essentially it's from master rate, so it should always be it's not from master. It's from.

C

B

From that bag from the deployed brand over finding a green build on master.

A

Ok, so there was the task to find the latest rebuilds on master, but for all of deploy, we're finding we're doing the pick into the auto deploy branch, and then we have this job near the funds, the green commit on one of the branch and then triggers a package of deployed. Yes, so it's on the it's on this branch. We look for the latest green commits right.

B

We can give a great event thing in your everyone, so it'll be a branch. Ok, I'll, be writing. That branch are the ribbon tiles right.

A

Yeah and those version files need to be updated and.

C

No, they can't be read and committed into omnibus that's what we get. That's.

A

What we do, alright, what is it, what does it mean.

B

A

Commit a dot on its.

C

Own basically I'm sorry.

B

We don't yeah, we don't commit an omnibus we pass. The values of the files to omnibus is trigger alright, for okay, so for.

C

Non-South managed release so for everything else. We can probably just pass the version file. Yes for.

D

A

C

Specialist all.

A

Right another piece, the trigger for many of us, it's a time that triggers like the act of tagging, omnibus. We figured if I record.

B

A thing I don't understand, though: you agree that we read the verdict files and then it triggered something with a prayer. It triggers a.

E

Bill for hummus all.

D

Right that bicycle or she uses the.

E

Nightly process and uses that as a jogger.

C

Okay, all right, so it's.

B

Like not like, we could have overloaded words for stop. Let's, let's.

C

Try to crank back I, get where, where the confusion is coming from. There are too many moving parts.

C

C

Know this is confusing because we were doing a lot of good runs and doing a lot of building on top of things that are already confusing. All right.

C

Problem, we are talking about dr. De Laurentiis right. Yes,.

C

A

Have we created a lot of a playground that we can use an example to like that planning a passing? Yes, so let's go it's 11 best end of it so for 11.10 top 11 10, the tie is done listening.

C

Hello stammers photo.

A

Deploy pipeline indeed, that's it.

A

We just removed.

C

C

So we create the occupy branch right automatically on schedule. The next thing is, we also have a schedule that will initiate the release by finding the latest dream commitment on particular branch.

C

All right- and this is in release tools- is that correct? Yes, so what this does is, it picks all the versions and it stores them in an environmental variable of some soldiers all right. So, let's see rails.

C

After the boy branch, it gets right, 11, no.

B

It's not is going to be it's going.

C

To be a great example where it's like.

B

C

This shop here is the real solution right all right, so.

C

Shop and then workhorse.

C

We we should be because it's important and then it says it's whatever.

B

A

Dot see these things every with Antonio.

C

Knows right, so this now needs to do like once. You actually found all these details. It is going to trigger a built.

B

Really girl pipeline and the Omnibus pipeline right, correct.

C

But wait all these versions passed into the built I thought.

A

Time being triggered the pipeline, because when they looked at how we do tax releases.

C

And also came to live in my plane as well.

A

This is keep on changing. Like I thought we were tagging the Omnibus he's.

C

There a reason why we can have like that in, like you, can.

B

Say you can I thought we were Paramore purposes of like here's. What change my thing is to very it's, not her building, nervously, okay,.

C

I'm having a bit of trouble understanding where, where the confusion is coming from, because this is fine, it just needs another step in between, and that is now that you finally found all this. We have all of the versions that you just shown. You can just create the tag based on what we created here and pass the versions to that. The.

A

Thing is: is that when we now do a chat, ops, command tag or release? Is the Omnibus pipeline triggered, or does it take off by virtue of tagging on Venus.

C

By virtue of tagging and.

A

That's what I thought we were doing for the audit deploys the same thing and that's how but then we can change it but okay, why wouldn't we do it that way, it's the question and also does that mess up the way the versions are passed.

A

A

Thought yeah I made into something that we were just going to be tagging and that which is it's not hard to change I, just trying to think through, like the implications of triggering and like if we trigger the pipeline, then is it different than tagging and moving still tagged? The Omnibus remember make a sweet little bit. Why don't I get like we do with the.

B

Charleston and attack on.

A

B

Build things and the tags in the specific format, Ravens yeah.

A

So I change the pipeline they'll actually link to the pipeline in the delivery in the cosmic.

D

Channel and that's what's happening now, like I.

A

I tagged the ammos with a specific format, doesn't the auto deploy format and then it picks jobs that are necessary to build the illusion package and deploy pre-product the? Where does it at.

B

At that point, where does it pick up the virtual number? That's.

A

What I don't know yeah.

B

A

Assume that is looking the right is the same money, but so.

C

Alright, okay I think I understand where this is lesson.

B

There now we're basically repurposing the nightly build yep.

C

B

C

The 93r is a beautiful problem because it's very loose, so it just uses it just uses whatever you give it, whatever is in current being there in those files using the additional files. But then what.

B

Happens when we're giving at these other version numbers it uses.

E

Either the commas or yeah.

C

But it won't like if we can make it work like that, but it's.

D

C

Gonna make it consistent with the tag behavior, which is a problem like how the release tool behaves when you've tagged on official release like if we introduced this another option of how this behaves, then it's going to be confusing even more correct without yeah and I. Also, really don't want to change the.

B

Release tools like official, like monthly tagging behavior, that's just.

B

C

So a question before you, then we we already use release tools to get those versions right. Then you print them out what is preventing us from just acquiring those things into the versions in omnibus clones repository and committing that and then pushing that there's a pack tagging and pushing that so long nervous.

A

Then the problem solved so he's tired, well yeah. So.

D

C

Other words, when all of the playbill is just like a really scary bit.

A

C

Know yeah, that's that's what, if we do this, so you have the Green commit stuff right, but it older versions.

D

B

That's triggered the pipeline in on a bus. Many of us is building the package with those version numbers that we've supplied pipeline trigger right.

B

If we actually built the package from the trigger yet.

E

Yeah little last-minute thinking.

B

I just passed true to this thing that the auto arranged.

E

I'm gonna take a few years, but something will do but.

D

Again, it's it's.

E

Abusing the use out of the trick definitely its abusing the nicely mental process so like the package it creates, has the word nightly and ready of it. Yeah.

C

But nightly is a bit different because we don't care about the version we just in omnibus all the version files are then pointing to master on all of those repositories. So we just pick whatever is latest in master in the satellite repositories, so.

A

Just so I'm clear when we do in our see when we tagged in our see what actually happens is is that we check out on the most and the update, the versions in on corrects I thought omnibus actually went to get by de using the tag and looked at the versions and get levy. No.

B

They don't have to clone.

A

Live a UW, yeah, well I, I guess like.

C

A

Painting switching to it trigger, if that makes it easier, but but the tag is not.

C

Going to be consistent with what is built, so you go and open a tag in omnibus the version file is gonna, say something different to what you actually build.

A

Yeah, so that is nice to update the version file in omnibus right, yeah.

D

B

What you should ranch it on both yeah.

A

It's consistent so there's actually the same under deploy, branch and omnibus.

A

So this pipeline that I'm running now, which I link to in the fast food general, this is actually building with old versions.

C

Whatever version work, it's not building the older deploy.

A

In fact they just building whatever version is, in the other, to play branch for you. It's.

F

So in that side of what happens in here, we have branch for week, one somebody.

A

F

By the whatever work, the sights the bump, the version even a corner, if you try to push that a to you, although ploy gradually get a conflict, we'd say: okay, we always think diversion from the able to deploy a branch, no check this other stuff that may depend it might get confusing awaiting masters. You know 12 0, but I'm older the points 11 whatever week, but.

A

So why don't we create the auto deploy branch and then we're tagging releases of are bumping versions in the auto play.

D

A

Two, we create a new, auto deploy range from master and then we update version so I, don't think I'll never be conflicts. No.

F

This might mean to do paranoid because I don't think anybody ever bombs. The version I.

F

Also, don't think they were confused by this. So would you just explicitly say mistaken agrees? The older version is prioritized over the one from the source branch. Yes,.

A

F

So the version files.

D

A

Get merged back into master on the honor of the play bridge right.

D

A

That's probably how it works now. Buddy statement ranges right, yeah.

F

We never merge back from stable within I've, been.

B

Reading and reading.

C

Enough to name committing that's the only does so.

B

Thumb position can be like.

C

Expanding not really.

B

This is like all this really stuff signature, stable.

A

B

And master change long.

B

C

Potential to break our actual release, assisted.

C

Home business again.

C

And as a change, love returning for journeys are seaso, he ignores it. Probably if, if not, if it's not assembler right, if you give it so that's gonna, be anyone yeah, that's gonna, be.

A

Completely switch looking.

C

Its release tools in omnibus, taking the release, so all right, ensure branches, a stable branch. That's the problem! How do you classy the simple branch.

C

Right so that means eleventh and all the employee would just be allowed new tax table.

C

Because that's where we are getting the real special problem.

C

So can we just expand this together, so the thing is: there's a lot of logic there that you slide around in stable branches. We need to expand this to be.

C

Circling around the these, both of the coil branches and the only difference basically is we don't need that change, love behavior? We don't need anything other than ensuring that these branches exist on all remotes and that's the version step, but the retrigger, the green commits stuff and the two puzzles versions, and that we tacked based on the tags that we have here.

B

C

This one seemed like we do like if we just inherit this and override these look like yeah.

C

There's a lot of logic there that I've kind of forgotten about it's just the.

B

Other thing it just works and the tests or yeah there are tests work there. So is dissonant.

C

You know how this works yeah, so that's why we should probably not touch this arrow, but I'll just expand it for the use case. We we need here, so you have it from this class and.

C

It shouldn't be that much work to do because you already have a good.

C

B

I mean at that point over really, inheriting from this is like mom, be very.

D

Well, plumbing, or bothering and mopping very oh.

D

C

Keep forgetting about this.

C

I'd like to keep the deck, though these things for deploying makes things a way clear and simpler. You know many of us in the company if.

B

We have if we get what we have now, where it's triggering pipeline with environment variables, for each versions can we create in that an annotated tags or the message of the NFA facto.

C

Servers and we have that work and but then you go to a tag and you see the necessary yeah. You don't need this region see their version. Files are different.

C

Halloween, like we just have already festival this green yeah, so I envision, a new rig nest is just like many would say, release tag when you lose some, never teens during environments where it could just take a breath.

C

We didn't reflect the reason we just to have the release namespacing right.

C

So emerged: here's the release there we go attack.

B

So we all seen the canoe when you get yourself as a very majority view from.

B

But we need like an auto-tuned flavor I.

C

Mean I knew this is when the vo realize how much.

C

B

Your art, history, I think your guitar attacking your belt, though, like you can't see what.

B

C

Doing so violent but doesn't mean, but.

B

C

How long do those honor display things stick around legally them eventually discussing.

A

Those things I, don't know if.

B

They're ephemeral and apparently.

A

Around the tank has the shot at rain, so it's not so.

C

Maybe you're I need of a domestic message. Yeah might be good enough.

B

Well, I think that goes like night yeah.

C

Don't want to use the I word, but maybe we should just be to it. I mean this is the boring solution.

C

Hey you kill with us iterate another.

B

C

But just keeping.

D

C

And instead of life, now revamping the wheel I'm just having the tag, so we do tag this, but the tank message actually contains the version of these versions help annotate the tag with the unit.

A

Emergence it's overloading stuff, but really just.

B

Informational informational, oh yeah,.

C

No no I mean okay. Let's make this clear. Are you actually sure distracted? So, let's try to just make it clear. We would.

E

Not be updating.

C

The version files in omnibus, so we.

E

Would be past environment there.

C

We would be passing the version versions.

E

Of these components.

C

To the omnibus is a trigger, so they were still, they would still receive the proper versions, but we would just tag on whatever it is. They're internet, I.

A

Need to change the logic then, from trying to trigger for.

A

Branch originally and I switched the tag and might as well do triggers hey.

C

Dude, this is a development or consideration yeah.

A

B

We're already triggering hearing like it already build off the.

E

A

That's for the Knightly that this is for the 90 building stuff that find is latest. This is not the I mean.

C

Like I know, we.

A

Were gonna adapt that front deploy, but I always assumed the Nam to plate just like in our scene. Well, it.

C

Is a it is not like at the time I thought that would be the.

A

Simplest approach quitting I guess if.

C

He's not like a 9 foot because 19 does not have any version constraints so.

A

D

Just to be clear, the reason why we're doing it.

A

B

B

A

F

C

This relatively new right now that is for use as in using city years.

A

Please it's just not very useful for the complicated I.

C

Mean, let's not go there right now, let's dance! Actually let me do it this way. You.

A

Know again, great.

B

C

Let's do it this way.

B

What does it need to do? It updates the files in a branch yeah.

A

Yeah, so they would have to before tagging I guess it wouldn't any I think the files that didn't stop date and.

D

A

C

Which would think? Oh, can you open again? The omnibus emergency only was taking nothing for the family was taking where we have the diversion.

C

So we need to use the API before tagging.

C

Right and then cross off trigger.

C

All right, API call before this, if see.

B

Period always stands for call yeah for.

C

Me, at least, if you.

B

D

C

If you're cold before tagging,.

C

All right vehicle Tony was reborn on the order.

C

Because we want to sing sing anyway,.

A

Right so it's a protected, it's a protected branch, so it would get sick Tovar to death. If you made it on good luck, calm if.

B

It's a protected branch. Can we.

C

Come to them talk anyway, but.

B

If I can't happen on demand like we can't I can't update these files and then yeah bag. That's a problem right. What we can't, then we can't build immediately. Think it triggers thing: yeah, sucks, yeah! That's why the release process it pushes all remote yeah.

A

That sucks, because if you updated upon both it would be two different convinces and you have.

B

Conflict assuming the contents of the same or different, say this burger burger.