Associate pipeline schedules with bot users
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Release notes
Problem to solve
Pipeline are associated with actual users, but should typically outlast any individual user as organization structure changes. So pipeline schedules should generally belong to bot users. But they also need to be maintained. And today, anyone except the current owner and instance admins are required to take ownership of the pipeline schedule prior to editing.
Proposal
Add the ability to select a bot user identity when creating or editing pipeline schedules. This identity is the one that should be used to actually execute the pipeline (as opposed to the schedule creator's identity). More specifically, this should be a project access bot or a group access bot (or a service account when those are available)
The user creating or editing the schedule should be able to select
- bots from the current project if they are a maintainer or above, and
- bots from any parent group where they are a maintainer or above.
In addition, when editing a schedule, the user should not be required to take ownership of the schedule if the associated identity is a bot that they can manage.
Intended users
License Tier
Feature Usage Metrics
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.