We started using Pipeline schedules in my past job to regularly trigger pipelines to e.g. rebuild Docker build images, clear caches and other sorts where you no

We started using Pipeline schedules in my past job to regularly trigger pipelines to e.g. rebuild Docker build images, clear caches and other sorts where you normally need shell access to a cronjob. https://docs.gitlab.com/ee/ci/pipelines/schedules.html https://docs.gitlab.com/ee/ci/pipelines/schedules.html Similarly, you can trigger pipelines from various angles https://docs.gitlab.com/ee/ci/triggers/ https://docs.gitlab.com/ee/ci/triggers/ using the API. If you are looking to combine it with events on-demand, the webhooks may come in handy. https://docs.gitlab.com/ee/user/project/integrations/webhooks.html https://docs.gitlab.com/ee/user/project/integrations/webhook... Agreed, some adhoc actions are project specific, though you can programmatically walk through them in API client code, for example searching for a group and triggering all project's pipelines. https://python-gitlab.readthedocs.io/en/stable/gl_objects/groups.html https://python-gitlab.readthedocs.io/en/stable/gl_objects/gr... https://python-gitlab.readthedocs.io/en/stable/gl_objects/pipelines_and_jobs.html#triggers https://python-gitlab.readthedocs.io/en/stable/gl_objects/pi...