GitLab Pipeline Authoring group, 2 Feb 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Job status using exit code

Description

No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).

A

Hi everyone- this is dr shkovitz from the pipeline authoring team. Today, I'm gonna do a short speed run on one of one of the very popular features that we just released in 13.8, which is control job status using exit code.

A

Obviously you can read all about it on our release, post, 13.8 or in our documentation, but I'm here to give you a demo. So, let's start, as you can see, I've created a simple pre-stage pipeline. I can use the visualization type to see. So I have three stage three job very simple pipeline and the thing about this job is that this pipeline is that the first build job return, an exit code of 125, test job and deploy job will return and exit 0 and 0., so exit 125 or any other exit code.

A

Besides, zero means that the job will be failed. So if I'm gonna remove this for a second, if I'm going to run this pipeline, the first job- and I can use the lint here- the first job will return. The value of 125 means that this job will fail and it will fail the entire pipeline and the test and the deploy will not run at all and the pipeline will be failed.

A

Okay, so far so good. I hope now in 13.8, we've enhanced the allow failure, keyword, allow failure allowing a job to fail before 13.7.

A

It was able to receive only a true or false value, so right or wrong, but in terms of eight we've enhanced the allow failure keyword to receive a list of numerous exit codes.

A

So if I know the exit code that my job is running- and I don't want to fail this job and fail the entire pipeline, I can simply list all the exit codes that I know as a user should not fail the pipeline and if I'll go ahead and run this pipeline, the results- and I run it previously- can show it to you.

A

The result of this pipeline is that you see that the first build job with the exit code. Actually, it's failing, but it is called password warning allowing test job and deploy job to continue to earn, and this is what's important important is that it is, did not fail the entire pipeline.

A

Now, why is it so critical and why it is such a popular issue, and I can show you that the issue, the original issue and we've implemented a slightly different method. The original issue has more than one 156 advert. It was a very popular issue. Why is that?

A

Well, it appears that a lot of our users are using different jobs to run different scripts and not all scripts return exit 0., some scripts return, different exit code and those exit codes are not worth failing the entire pipeline, so they were in a they were in a kind of a problem.

A

They get like an exit code which is okay and should not fail the pipeline, and we failed the pipeline. Now. What we could do is we could tell them. Okay use the allow failure, okay, why shouldn't they use the allow failure to and get rid of all these exit codes, and the reason is that it depends on the exit code, because here it's either pass or fail, but this feature provide you with much bigger granularity.

A

So if you know the exit code, you can specify which exit code are like okay and will not fail the the pipeline in which exit codes are not okay and should completely fail the pipeline.

A

So this is it obviously, you can read all about it on our documentation and let us know what you think thanks bye.