I really appreciate the convenience of pipeline schedules in GitLab. They make my life easier for various tasks, but my concern is that they run under the user who created them. If that user leaves the company, all their scheduled pipelines break, which can be problematic. I heard that you can't run these pipelines under a bot user either. Besides making a service account specifically for pipeline schedules, what are some effective strategies to handle this situation?
5 Answers
One simple solution is to request a Technical Account and set up the pipelines under that account. It could save you from running into issues when someone leaves the company.
From what I've gathered, all scheduled pipelines are tied to jobs. You might consider just recreating them under a new user. I haven't been working with GitLab for long, but that's one approach.
You can create an access token and use it to set up the pipeline schedule via the API. Unlike user accounts, access tokens don’t have owners, so you only have to renew them once a year without having to recreate the schedules. Plus, with the API setup, you can manage your configurations as code, making it easier to handle.
While pipelines may break when a user leaves, you can easily adopt those scheduled pipelines. GitLab has documentation on how to take ownership of existing scheduled pipelines. It's a straightforward process to gain control over them again.
It’s definitely possible to use a bot user to run the pipelines. That’s what I’m currently doing! If you're interested, I can explain how I set mine up.
Related Questions
How To: Running Codex CLI on Windows with Azure OpenAI
Set Wordpress Featured Image Using Javascript
How To Fix PHP Random Being The Same
Why no WebP Support with Wordpress
Replace Wordpress Cron With Linux Cron
Customize Yoast Canonical URL Programmatically