GitLab API

GitlabTool
Join our community

Actions905

Overview

This node operation allows a user to take ownership of a specific pipeline schedule within a GitLab project. It is useful in scenarios where a user needs to assume control over a pipeline schedule that was created by another user, enabling them to manage or modify the schedule as needed. For example, a DevOps engineer might use this operation to take ownership of a pipeline schedule to update its timing or configuration.

Use Case Examples

  1. Taking ownership of a pipeline schedule in a project to update its settings or manage its execution.
  2. Assuming control of a pipeline schedule to troubleshoot or modify automated CI/CD workflows.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the request, useful for public or unauthenticated access.
Authentication Type of authentication used for the request, defaulting to GitLab API key authentication.
baseUrl The base URL of the GitLab instance, defaulting to https://gitlab.com.
Method HTTP method used for the request, default is POST to take ownership.
Path Parameters Parameters required in the URL path to identify the project and pipeline schedule to take ownership of.

Output

JSON

  • id - The ID of the pipeline schedule that ownership was taken for.
  • project_id - The ID of the project containing the pipeline schedule.
  • owner - Information about the new owner of the pipeline schedule.
  • status - The status of the pipeline schedule after taking ownership.

Dependencies

  • GitLab API key credential for authentication

Troubleshooting

  • Ensure the project ID and pipeline schedule ID are correct and exist in the GitLab instance.
  • Verify that the API key used has sufficient permissions to take ownership of pipeline schedules.
  • Check network connectivity to the GitLab instance base URL.
  • If authentication is skipped, ensure the endpoint allows unauthenticated access, otherwise the request will fail.

Links

Discussion