CI Update job trigger conditions

Development
#1

The “CI Update” job runs via cronjob every Sunday, but also via “Manually run by pulpbot”: https://github.com/pulp/pulp_deb/actions/workflows/update_ci.yml

My question is: What causes “Manually run by pulpbot”, and ist this really necessary? It happens annoyingly often, and there are too many “Update CI files” commits in the pulp_deb history, relative to actual code changes.

#2

I trigger it here: https://github.com/pulp/plugin_template/actions/workflows/update_ci.yml whenever a change that may fix multiple CIs is merged on plugin-template. Last time it was the fix for upgrade tests

2 Likes
#3

Ahh! That flow actually makes a lot of sense. Maybe I can learn to be more tolerant of it, now that I know the background. :grinning_face_with_smiling_eyes: