Skip to content

Define ownership for schedules #1223

@AlbertoCortina

Description

@AlbertoCortina

Summary

Allow defining the owner of a pipeline schedule directly in GitLabForm.

Motivation

Currently, schedules are owned by the user who creates them, and ownership cannot be set declaratively. This makes it difficult to manage schedules in team environments or when responsibilities change.

I’m not sure if this feature has already been requested before, but it would be very useful for teams managing CI/CD declaratively.

GitLab already provides an API to update/take ownership of a pipeline schedule:
https://docs.gitlab.com/api/pipeline_schedules/#update-ownership-of-a-pipeline-schedule
However, this capability is not exposed through GitLabForm.

Proposed Solution

Add support for an owner (or similar) field in pipeline schedule definitions, which uses the GitLab API to assign or transfer ownership.

Example

schedules:
  enforce: true
  "Scheduled deployment":
    ref: main
    cron: "0 19 * * MON-THU"
    cron_timezone: "Europe/Zurich"
    active: true
    owner: "test user"

Thanks for considering this improvement!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions