GitLab API icon

GitLab API

Gitlab

Actions917

Overview

This node interacts with the GitLab API to perform a ping operation on the Conan packages endpoint for a specific project. It is useful for checking the availability or status of the Conan package registry for a given GitLab project. For example, it can be used to verify connectivity or readiness of the Conan package service within a CI/CD pipeline or automation workflow.

Use Case Examples

  1. Check the Conan package registry status for a project before publishing packages.
  2. Verify connectivity to the Conan package endpoint as part of a deployment process.

Properties

Name Meaning
Skip Authentication Option to skip authentication when making the API request.
Authentication Type of authentication to use for the API request, hidden unless Skip Authentication is false.
baseUrl Base URL of the GitLab instance to which the API request is sent.
Method HTTP method used for the API request.
Parameter Schema Schema defining the path parameter 'id' which is the ID or URL-encoded path of the project.
Request Body Schema Schema for the request body, null for this operation as it does not require a body.
Request Path API endpoint path with a placeholder for the project ID.
Path Parameters Collection of path parameters including 'id' which specifies the project identifier.

Output

JSON

  • response - The JSON response from the GitLab API ping endpoint for the Conan packages of the specified project.

Dependencies

  • GitLab API authentication token or credentials

Troubleshooting

  • Ensure the project ID provided in the path parameters is correct and accessible with the provided authentication.
  • If authentication is skipped, the API request may fail due to lack of permissions.
  • Verify the baseUrl is correct and points to a valid GitLab instance.
  • Common error messages may include 401 Unauthorized (authentication issues), 404 Not Found (invalid project ID or endpoint), or 500 Internal Server Error (server issues).

Links

Discussion