Required status checks, reusable workflows and skipped jobs

[markgoddard]

Select Topic Area

Product Feedback

Body

I have a PR workflow that calls several other reusable workflows. There is a dependency from the all-in-one-* jobs on the build-kayobe-image job. Each job is listed as a required status check.

Since these jobs take a long time, I'm trying to add path filtering to run certain jobs when particular files changed.

At first, I tried the workflow-level path filtering. This is a nice feature but does not work with my reusable workflows because the name of the check differs depending on whether the job is skipped or not.

e.g. When the all-in-one-centos-ovs job in the outer workflow runs, it registers a check as aio (CentOS OVS) / All in one. However if the job is skipped, it registers as aio (CentOS OVS) and I still see the aio (CentOS OVS) / All in one job as Expected — Waiting for status to be reported.

Next, I tried using the dorny/paths-filter action to conditionally skip jobs. This suffers from the same problem with job naming, but I was able to work around it by passing a skip condition into the reusable job.

I also had to add an always() condition to the dependent jobs to avoid them being skipped if the parent job is skipped. I'm unsure if this is a good solution.

I believe this is now doing what I want, but it doesn't seem like an ideal solution.

[markgoddard]

Follow up: always() didn't work in the case where the parent job failed, so I switched to ! failure(), and this seems to be working. Here is the result.

[dja557]

I have the same problem. I ended up creating my own status checks using the GH CLI based on success or not. This works but again, not an ideal solution at all.

[Fresa]

Agree, skipped jobs are not being reported with the reusable workflow job's name included. I guess it's never evaluated when the calling job's condition is not fulfilled.

These two are "the same check", the first one get's reported when the job is skipped, the second one when it runs.