GitLab API

GitlabTool
Join our community

Actions1000

Overview

This node operation allows updating the Drone CI service integration settings for a specific GitLab project by making a PUT request to the GitLab API endpoint `/api/v4/projects/{id}/services/drone-ci`. It is useful for automating the configuration of Drone CI integration within GitLab projects, such as enabling or modifying CI/CD pipeline settings programmatically.

Use Case Examples

  1. Automatically update Drone CI integration settings for multiple GitLab projects in a batch workflow.
  2. Modify the Drone CI service configuration as part of a deployment pipeline to ensure consistent CI settings across projects.

Properties

Name Meaning
Skip Authentication Determines whether to skip API authentication for the request.
Authentication Specifies the authentication method to use, defaulting to GitLab API key authentication.
baseUrl The base URL of the GitLab instance to which the API request is sent, defaulting to https://gitlab.com.
Method HTTP method used for the request, defaulting to PUT for this operation.
Path Parameters Parameters included in the request path, specifically the project ID to identify which project's Drone CI service to update.

Output

JSON

  • id - The ID of the GitLab project for which the Drone CI service integration was updated.
  • service_status - The status or result of the update operation on the Drone CI service integration.
  • updated_fields - Details of the fields that were updated in the Drone CI service configuration.

Dependencies

  • GitLab API key credential

Troubleshooting

  • Ensure the project ID provided in the path parameters is valid and accessible with the authenticated user or token.
  • Verify that the API key credential has sufficient permissions to update project service integrations.
  • Check the base URL to confirm it points to the correct GitLab instance, especially if using a self-hosted GitLab server.
  • Common error messages include 401 Unauthorized (authentication issues), 404 Not Found (invalid project ID or service endpoint), and 400 Bad Request (invalid request body or parameters). Resolving these involves verifying credentials, project existence, and request payload correctness.

Links

Discussion