GitLab API

GitlabTool

Actions905

Overview

This node operation retrieves detailed information about a specific Conan package from a GitLab project using the GitLab API. It is useful for developers and DevOps teams who manage Conan packages within GitLab projects and need to programmatically access package metadata or details for automation, auditing, or integration purposes. For example, it can be used to fetch package details during a CI/CD pipeline to verify package versions or to integrate package data into other systems.

Use Case Examples

  1. Fetch details of a Conan package version '1.0' named 'my-package' in a GitLab project with ID '123', under the username 'my-group+my-project' and channel 'stable'.
  2. Automate retrieval of Conan package metadata for auditing or reporting in a DevOps workflow.

Properties

Name Meaning
Skip Authentication Whether to skip authentication when making the API request.
Authentication The authentication method used for the API request, typically an API key credential for GitLab.
baseUrl The base URL of the GitLab instance to which the API request is sent.
Method The HTTP method used for the API request, default is GET.
Path Parameters Parameters required in the API request path to identify the specific Conan package.

Output

JSON

  • id - The ID of the Conan package.
  • package_name - The name of the Conan package.
  • package_version - The version of the Conan package.
  • package_username - The username or group associated with the package.
  • package_channel - The channel of the Conan package.
  • conan_package_reference - The unique reference ID of the Conan package.
  • metadata - Additional metadata and details about the Conan package returned by the API.

Dependencies

  • GitLab API authentication token or API key credential

Troubleshooting

  • Ensure all required path parameters (project ID, package name, version, username, channel, and package reference) are correctly provided; missing or incorrect parameters will cause API errors.
  • Authentication errors may occur if the API token is invalid or missing; verify the GitLab API credentials are correctly configured.
  • Network or base URL issues can cause request failures; confirm the baseUrl is correct and accessible.
  • API rate limits or permission issues may result in access denied errors; ensure the API token has sufficient permissions to access the project and package.

Links

Discussion