GitLab Speed Runs, 18 Aug 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Speed run: CI lint tool handling of warning and errors & simulation

Description

https://gitlab.com/gitlab-org/gitlab/-/issues/219431 and https://gitlab.com/gitlab-org/gitlab/-/issues/229794

A

My name is jason yavarska and I'm the product director for cacd.

A

That's my son back there and um what I want to record today is a quick speedline of our new um some improvements to the uh validation of the galapagos, the linter, um the there's a couple new things here that I'll show one is uh that there's we have the simulate button uh which will run a pipeline as if uh it was processed for real uh and then the other is some new warnings. um So, uh let's start by uh just writing a basic pipeline here. So um um so I'll just say: that's alpine!

A

I'm not actually gonna run this, so uh it doesn't really matter too much what I'm doing section.

A

Okay! um So now uh I can validate uh that this is a valid yam, well, which you could do before this existed before.

A

I'm also able to simulate a pipeline, though, which is a new, interesting thing, and what this is doing uh is it's actually evaluating the pipeline as if it would have run in the project, so you have to have permissions to actually run a pipeline in the project to test in this mode, um but where you can see the benefit of this is, if you start to do things uh where um you know, if you say rules, if um you know my variable is equal to true, uh then go ahead and uh always run this.

A

um You know if you, if you just validate this in the old way. um Oh sorry.

A

Trusty linter: okay, if you validate this in the old way, it just validates that the syntax is good and it's fine. But um if you validate this using a simulation, you'll see that uh no jobs resolved to existing for this pipeline. That's because this variable is not true, and this is the only job.

A

So I could prove this out by adding a variable section and setting a variable to true. And now, if I simulate this again, it should result yeah and now there's a job instantiated based on this rules being evaluated to true, uh which is cool. um The other thing that you can do here is um we've added warnings. So uh if I have a job too- and I do something like.

A

Hello and then rules.

A

And just set this to always run, uh we should get a warning here.

A

A

Yeah, I get a warning that uh this can allow multiple pipelines to run, uh because when always the resulting into true um means that it will run for a merge request pipeline, it will run for a regular pipeline. Then you can read more. uh We link to the instructions here, um so these warnings are new and we're going to be adding more and of these things and um yeah.

A

I hope that these are uh nice new features that you can use and help make your authoring experience a little bit easier uh thanks for watching and um would love to hear your feedback on these. Thank you.