GitLab API icon

GitLab API

Gitlab
Join our community

Actions917

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 previously owned by another user or when managing project automation schedules. For example, a DevOps engineer might use this to take ownership of a pipeline schedule to modify or maintain it.

Use Case Examples

  1. Taking ownership of a pipeline schedule in a project to update its configuration or manage its execution.
  2. Assuming control of a pipeline schedule after a team member leaves or changes roles.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the request.
Authentication Type of authentication used, default is GitLab API key.
baseUrl Base URL of the GitLab instance, default is https://gitlab.com.
Method HTTP method to use for the request, default is GET but POST is used for this operation.
Path Parameters Parameters for the API path including project ID and pipeline schedule ID.

Output

JSON

  • id - The ID of the pipeline schedule taken ownership of.
  • project_id - The ID of the project containing the pipeline schedule.
  • owner - Information about the new owner of the pipeline schedule.
  • status - Current status of the pipeline schedule.

Dependencies

  • GitLab API key credential for authentication

Troubleshooting

  • Ensure the project ID and pipeline schedule ID are correct and exist in GitLab.
  • Verify that the API key has sufficient permissions to take ownership of pipeline schedules.
  • Check network connectivity to the GitLab instance specified by the baseUrl.
  • Common error: 404 Not Found - The project or pipeline schedule ID does not exist or is inaccessible.
  • Common error: 403 Forbidden - The API key does not have permission to take ownership of the pipeline schedule.

Links

Discussion