09:02 <alatiera_afk[m]> David Heidelberg: in case you might know, is there an easy way to make a pipeline/scheduled with a single job without adding if "UPDATE_JOB != 1" to all the rest of the pipeline jobs?

09:04 <DavidHeidelberg[m]> alatiera_afk: do you have example where you try to implement it? Thou if I understand right, I think there isn't.

09:06 <alatiera_afk[m]> David Heidelberg: yea, like this for example https://gitlab.gnome.org/GNOME/gnome-build-meta/-/merge_requests/1825/diffs#587d266bb27a4dc3022bbed44dfa19849df3044c_508_515

09:06 <alatiera_afk[m]> ie, have a job in the CI that can run on its on a schedule without triggering everything else

09:06 <alatiera_afk[m]> cause its gonna make an MR anyway

09:06 <DavidHeidelberg[m]> ok, I have idea. You could use workflow:rules

09:06 <alatiera_afk[m]> oh inded

09:07 <DavidHeidelberg[m]> set everything as no-scheduled. And then override the specific job

09:07 <alatiera_afk[m]> although doesn't that mean that the whole pipeline will be filtered out?

09:07 <alatiera_afk[m]> workflow:rules are pipeline wide iirc

09:08 <alatiera_afk[m]> so then the jobs triggered from the schedule will come back again

09:08 <DavidHeidelberg[m]> yup. So you say NO every job in pipeline, and then YES to one specific

09:08 <DavidHeidelberg[m]> let me check the merged mesa yml

09:10 <DavidHeidelberg[m]> you can use variable for that. Look at mesa and MESA_CI_PERFORMANCE_ENABLED

09:11 <alatiera_afk[m]> David Heidelberg: but you need to add that to all the job rules too right

09:11 <DavidHeidelberg[m]> yeah, yeah :(

09:11 <alatiera_afk[m]> hmm, indeed no nice way then

09:11 <DavidHeidelberg[m]> doing simple stuff isn't GitLab thing..

09:12 <alatiera_afk[m]> ikr

09:12 <alatiera_afk[m]> meanwhile on github you can write scripts to execute in templates, that are not inlined bash or wgetted

09:12 <alatiera_afk[m]> and have standalone jobs trigger on events

09:13 <DavidHeidelberg[m]> maybe if you wait 1-2 hours, gallo will be up and he could have some idea

15:56 <gallo[m]> alatiera_afk: we do kind of the same thing with stage granularity in mesa-performance-tracking. The jobs on later stages inherit .stage-only-rules, see https://gitlab.freedesktop.org/gfx-ci/mesa-performance-tracking/-/blob/master/.gitlab-ci.yml#L17 . If you are targeting a specific job name in your scheduled pipeline, you can use the same trick by replacing $CI_JOB_STAGE with $CI_JOB_NAME.

15:56 <alatiera_afk[m]> gallo: oh that's a good one, thanks for the pointer

15:57 <gallo[m]> np! let me know if it worked or not.

16:05 <alatiera> will do, probably will look into it tmr

19:42 <__tim> if I want to find out what jobs were running on a particular gitlab-runner at a particular time, is there an easy way to query that? (or does someone have a script?)