Skip to content

Fix rules for the unit test job

What does this MR do?

This is another followup to these two MRs:

The goal is to improve pipelines for forks by limiting the number of jobs that run that require our own runners. We decided to still let the unit test job run and give our contributors some early feedback, but I got the config wrong in the earlier pipelines.

I fixed one detail in !5608 (merged), but now I see that unit test is trying to run in docs pipelines (incorrectly): !5617 (merged)

It seems the single quotes in the new rule caused the regex to not be parsed properly, so I've removed that, and tested it in this docs MR (targeting this MR's branch):

At the same time, I don't think I got the unit test job's original rules right either, so I've copy pasted from the correct place, see the note below.

Why was this MR needed?

What's the best way to test this MR?

What are the relevant issue numbers?

Edited by Marcel Amirault

Merge request reports

Loading