Skip to content

ci: Add a trigger job

Previously we were using the same image rules for the 'build docker' stage, and since those jobs wouldn't trigger, the pipeline would not advance further.

However in eab82268 we defined needs: for the rest of the jobs so they can start asynchronously, which caused the jobs to always execute, since they didn't have an image build job to wait upon.

Add a trigger, no-op, job that any job can depend and to switch back to the previous behavior.

Merge request reports

Loading