Follow-up from "ci: do not pass --report-errors to both jobs"
@eric: Nah, that still didn't do the trick, we were just unlucky and GNOME fixed their blogs at a bad time. Now we have a new issue: https://gitlab.freedesktop.org/freedesktop/planet.freedesktop.org/-/pipelines/991307
Is that exactly what we want? Fail the pipeline but still execute the pages job so that we keep updating other blogs?
Maybe that's what was implemented, but it's not what I'd expect, at least.
What I'd expect, is as follows:
- The "test-disallow-failures"-job should not run for the cron-job at all. Doing that should be completely redundant, because the failure does nothing useful, and updating twice for all.
- The "test" job to be marked with a warning.
But thinking about it again, we actually fetch all the blogs three times now, in "test", "test-disallow-failures" and in "pages". For the cron-job, doing this once should be plenty. IIRC, there were some issues getting the pages job to deal with allow-failures, but then we should have the pages job simply forward artifacts from a previous job, rather than building again.
So I think the jobs should really be:
- "test": No failures allowed, only runs on MRs.
- "build": Failures allowed, only runs on main. Uploads artifacts.
- "pages": Consumes the artifacts from "build", only runs on main.
Right now we're just contributing to melting the polar caps for no good reason.