GitLab Verify Group, 11 Jun 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Speed run of project pipeline subscriptions

Description

https://about.gitlab.com/releases/2020/04/22/gitlab-12-10-released/#automatically-trigger-your-project-when-another-is-rebuilt

Implemented via https://gitlab.com/gitlab-org/gitlab/-/issues/9045

A

Hey everyone, my name is jason yavorska and I'm the product director for ci cd at get lab, uh and today I'm gonna record a feature that was released in uh 12.8. It looks like where you can trigger a pipeline when another project is rebuilt and the reason that you would do this is because you are dependent on some artifact that's produced in uh in that upstream build, and so you want to grab it and you want to um you want to to use it in your own project.

A

uh So, um let's start by creating a new project. I guess I'll need two new projects.

A

B

Dependency and project uh depends, um these can be public and initiated with the readme.

A

So the project depends will depend on the project dependency. So let's get this one set up first, so um we'll start with the job, just something basic image alpine and we'll say: build stage scripts.

A

um Let's create a file called.

A

Hello and my artifact, obviously this is.

A

um Obviously this is uh it's kind of fake, but we'll we'll, try and grab this my artifact and we will uh try and do something with it. um So I think.

B

This will work.

A

We might need to double check the uh the syntax if I missed something here, let's look at the pipelines for this project. Okay, that is.

A

Running uh and then, while that's going, let's start working on this one, actually, I'm going to grab the gitlab ciem. I just.

B

Made all right um back to pipelines, set up ci cd.

A

um So this, then, will be the one that we described so this one will want to do something like I don't know if rot13 or something isn't installed on uh on alpine by default, I'm actually sure probably sure it's not, but let's just do something simple like copy my artifact to my processed artifact and then that my process not actually doing any processing but just to kind of get the um get a sense of what's going on here, um my processed artifact.

A

Actually, we don't really need to cut it since we're creating this, so um this is gonna fail until we set up the subscription, but that's okay. We can just kind of confirm that um okay, so this past looks like it did, make artifacts. So, let's see all right it did. It created an artifact here, let's browse just to make sure that everything looks as expected.

A

um It's just a text file, probably because I didn't put a dot text extension on it. It's not showing it um but fine, okay, great! So then, let's go set up our dependency, so setting cicd page and expand the pipeline subscription section.

A

Pipeline subscriptions okay, great um the project path, I guess is um jayavariska.

B

Slash project dependency.

A

Two subscriptions from our two project: that's a very low limit. um Let's see if this works.

A

What did that? Do I clicked? um Oh it it collapsed it after I did it.

A

Okay, I think that that worked. um It would be better. Obviously, if it didn't collapse it after you did that so that you could see what it just did, but um but that's sort of a minor ux problem.

A

um Okay, uh so we have this dependency. Now, let's go back. uh Let's look at our pipelines here. um I guess that it will have failed because there is no file to copy um yep yeah, no such file. Okay, let's go over here.

A

um Let's build this again and hopefully what happened there? uh Hopefully what we see is. um It will finish because we're running on the master branch, which is a requirement for this feature, then it will trigger a pipeline that depends on the other over here once this is.

A

Finished uh we we shouldn't need to do anything to um bring the artifact over. I would hope, uh since this whole feature is about kind of like doing something with the output of another one, um but but we'll see, um I'm wondering a bit okay, so that finished great there's something starting.

A

B

A

Yet, let's double check our subscription.

A

Okay, it says it has it.

A

There may be some, you know, processing happening to to wire them together, but I would sort of expect it to have started by now. We'll give it another minute. um Let's look at the docs again in the meantime,.

A

So you can trigger your pipeline, your project neurons, another one finishes.

A

Any pipelines that complete successfully for new tags- um oh so there has to be a new tag. Okay, um that's.

B

B

A

See so you can create a tag by creating a release.

A

Tag name: let's call it 1.0 um sure.

A

All right, so we have a 1.0 release. The releases feature is great. By the way I didn't show some of the cool things that it has. It can show release notes. It can show a lot of really interesting things about about what was in that tag, as well as link to like things that are in progress and um and more reports, but that's a subject for another another another day.

A

Okay, so one thing that's confusing about the the docs here.

A

The feature says trigger a pipeline when an upstream project is rebuilt, um but that's not really what it is. It's trigger a pipeline or it's not really what was built. It's trigger a pipeline when an upstream project gets a new tag. um So possibly we want to clear up the docks here: um okay, great um and it ran- which is good, but um it doesn't look like it actually grabbed the artifact, um which is unfortunate.

A

I don't know for following up on that in another release, but I would expect that yeah again that um if you, um if you're setting this up, there's this relationship up, that artifacts would would come, um but uh we can make this work in another way. So we need to look at the ciamo docs and.

A

A

I saw something there about cross project, artifact, download yeah so see. This is what I would have expected to happen that the cross project artifacts would have been automatically grabbed um because um it um yeah again. That's the that's the point of the the feature.

A

Pipelines in different projects- okay, so I think this is the the syntax that we need here. um Let's see if we can get this working by manually, putting it in there.

A

So needs the project is, um is going to be uh j, horsco, slash, project dependency, the job is called build. The ref is master, though we sort of want, like, I guess, to know the tag. That's that we're building. Well, I guess this is when a new tag is created, so this will work.

A

This isn't exactly what this isn't exactly correct, though right, because if you, you could imagine a situation where two tags are created in quick succession, um then you're getting the wrong tag because you're getting the one for master instead of the one for um the specific tag, but I don't know how you would get the um I don't know if there's a variable that contains the tag that um represents the tag in the other project. um There's nothing documented about that.

A

um So maybe that's a that's an improvement that could happen, um but let's try this um apologize for all the commitments that is being default. I wouldn't normally do that, but um okay, um so this will run um we're not retesting the uh um the triggering, because we saw that that worked.

A

um But let's see if we can grab that artifact now and actually um do something with it and produce a processed artifact or a downstream artifact.

A

Hopefully, hopefully, this works. um What I would recommend is that, on this section we we mention here that um something about using if needs works, um that we mentioned something about hey, and you know you probably want the artifacts. So if you want the artifacts, then um also you know use that needs uh needs section. Okay,.

B

So yeah now it worked.

A

uh We grabbed the my artifact and we turned it into my processed artifact um and we downloaded it um so, let's, uh let's actually open this up now and see, uh see what we get hello. Okay, so just as expected, um great uh so yeah pretty cool a couple minor things about the documentation: either we need to make the um artifacts downloaded automatically when you do this or document how to get the artifacts in the way that I that I set it up and and yeah.

A

I think there was one or one or two other minor things that we ran across as we were testing this out, but cool feature. I'm really excited to have released this recently, uh thanks for watching and uh until next time.