GitLab API

GitlabTool
Join our community

Actions1000

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 configuration or troubleshoot issues.

Use Case Examples

  1. Taking ownership of a pipeline schedule in a project to update its timing or parameters.
  2. Assuming control of a pipeline schedule to disable or delete it when the original owner is unavailable.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the request.
Authentication Specifies the authentication method to use, typically an API key credential for GitLab.
baseUrl The base URL of the GitLab instance, defaulting to https://gitlab.com.
Method HTTP method to use for the request, default is GET but POST is used for this operation.
Path Parameters Parameters required in the URL path to identify the project and pipeline schedule.

Output

JSON

  • statusCode - HTTP response status code indicating the result of the ownership request.
  • body - Response body containing details about the pipeline schedule ownership change or error information.

Dependencies

  • GitLab API authentication token or credentials

Troubleshooting

  • Ensure the project ID and pipeline schedule ID are correct and exist in the GitLab instance.
  • Verify that the authentication credentials have sufficient permissions to take ownership of the pipeline schedule.
  • Check the base URL to confirm it points to the correct GitLab instance.
  • Common error messages include 404 Not Found if the project or pipeline schedule does not exist, and 403 Forbidden if the user lacks permission to take ownership.

Links

Discussion