GitLab Speed Runs, 28 Jul 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Speed run for matrix builds

Description

https://docs.gitlab.com/ee/ci/yaml/#parallel-matrix-jobs

A

Hey everyone: my name is jason jovoska and we're going to do I'm here with todd yeager we'll introduce yourself in just a moment and um we're going to do a speed run of the new parallel builds feature.

A

Introduce yourself.

B

I'm tali yeager, I'm co-pm um for continuous integration.

A

Right and I am the product director for cicd, um so the first thing we need is the docs for.

A

For the parallel keyword um here.

B

Or for the matrix keyword.

A

All right here it is there's an example here as well. um I'm cheating a bit I like to do. Speed runs blind, um but I've done one before, but I've only done one before so it's semi-blind um and so the project name. We can call this demo matrix and make.

B

A

Public project initialize it with the readme, then what we need to do is add a gitlab cio and we want to just do something interesting, that's kind of like this.

A

So um what the matrix feature does is it lets? You define a number of elements um that interact with each other, so the classic example is like architectures and then like debugging release or whatever.

A

Is there anything that you want to try cal um that we could get working.

B

uh I not really I I thought. One of the things we would do on the speed run is also validate the documentation and use what they have there to make sure that at least is.

A

Just going to reduce this yeah well, I would say that's more of like a test um doing a speedrun.

B

A

Adapting it to some use that you have in checking the documentation, but there's not much documentation to it. Okay,.

B

A

B

I don't I didn't have this.

A

Example and then says you know just do the same thing so uh yeah, so we can make an example. That's just like. um Let's say we have a build and then we have a test. We have a well.

B

Let's just keep it simple.

A

A

A

B

Script should do something.

A

um I don't know the indication is.

A

B

Was going to ask you um it's weird that.

A

You're editing, your guillaume ciamo and it's doing the wrong annotation. So maybe that's like a interaction bug that we should open an issue for um yeah and then so the script does need to do something.

A

um So we could just say echo hello,.

A

And then now we use the parallel keyword and then.

B

A

And here is very annoying uh here we um can have all of our elements, so provider stack each one of these things within the matrix is a variable that will get set. uh So we could say target is one for us and then maybe um architecture uh as an example, uh and then we could say um yeah. I think that's sufficient. Probably um so the way you do this is, you say: you've got a colon and an array afterwards.

B

You could do this this way.

A

And list your architectures, um but it's kind of nice just do it this way. So we can say: um windows, linux,.

A

Platform, maybe windows, linux android. If we imagine that we've got some kind of um you know mobile and web app, and then we could say for each of these we want uh a debug and a release build.

A

um So then what this should do uh and we can change this a little bit more interesting echo. I.

A

Kind of like little combo like this, the way you had to do this before was create a job for each of these, so you'd end up having you know, there's two times four, so you end up having eight jobs uh manually written here that you had to keep in sync, and you probably use an anchor or something like that to have the boilerplate.

B

A

Just makes it much easier: um let's check check our instructions, one more time and make sure we're not missing anything.

A

Oh actually, I do have one thing going here, so each one of the matrix um entries here in the array represents one combo. So I shouldn't I should have it like this and then I could have another combo here. That's like another set. um So let's say: we've got.

B

Okay, so in the example they had three combos.

A

Yeah they do okay, okay, uh let's say another uh platform is: um oh, I don't know um something else and then uh that only supports having a release fund. um So you could build your combo like this, and these should get added together. um So we should end up with debug and release windows, debug and release linux and so on, and then cut release for something else.

A

B

Then it should.

A

Generate these jobs.

B

Yeah, I do want to try so in the example. uh Instead of doing a uh array, they yeah, they did. um They indented yeah.

A

Because it's an array of one uh so that should work you're right, that's a simpler, simpler way to oh- and you can do the same here actually also.

B

A

Yep, okay, anything else you want to try here.

B

um Is is the reason in the example it's indented below like say the last, the last comb will you there for a platform, because it has more than one like uh under stack monitoring api one api, two.

A

Or app one episode you could have written it this way. Also, okay,.

B

A

Showing that you can write it both this is an array in yaml, and this is another animal. So there are just like two equivalent ways to write the same thing.

B

A

Okay, let's try it. uh Hopefully we don't have some there. I usually do uh when I try one of these games, but let's see then.

B

We want to see the pipeline.

A

Hey uh no yaml, I got nice and then, if we look at this.

B

Yeah we have our nine. We see that.

A

Interaction bug here um where it's like there's all of this white space down here for some reason: yeah, um but that can be fixed. It looks like they're all running and passing, which is as expected. um It's called build 109 and I think that's actually wrong.

A

I was going to build debug for windows yep. um You know this will be some other random thing. I was.

B

Gonna build debug for android yeah, so it's.

A

uh It's getting the variables and and seems to be showing it quickly. uh One thing that I'm seeing here that's a little different. It looks like for one. This retry button is in the wrong place.

A

I think it's like up high kind of off of the.

B

I see yeah, it's looks like it's like.

A

And then, actually, if you go all the way to the top, it's cut off, even so, it's too high for some reason, the minor minor ux thing uh and the other thing is it's not showing the job name like this, um or maybe this isn't implying that this is the job name. uh I know that, there's a so I happen to know that there's a follow-up issue to make these job names more descriptive, um but that's an issue with the documentation.

A

Now, uh if this is because it's only doing this part of the documentation, there is a follow-up to add this part.

B

A

um You know the documentation seems to be saying that he exists, so maybe that's appreciated.

A

And that's it, that's a speed run um yeah! Oh.

B

A