GitLab API icon

GitLab API

Gitlab
Join our community

Actions880

Overview

This node operation retrieves detailed information about a specific Conan package from the GitLab API. It is useful for developers and DevOps engineers who need to access package metadata stored in GitLab's Conan package registry. For example, it can be used to fetch version details, user information, and channel data for a particular Conan package reference.

Use Case Examples

  1. Fetching metadata for a Conan package named 'my-package' with version '1.0' under the user 'my-group+my-project' and channel 'stable'.
  2. Automating package version checks in CI/CD pipelines by retrieving package details from GitLab.

Properties

Name Meaning
Skip Authentication Determines whether to skip authentication when making the API request.
baseUrl The base URL of the GitLab instance, defaulting to https://gitlab.com.
Method HTTP method to use for the request, default is GET.
Path Parameters Parameters required in the API path to specify the Conan package details.

Output

JSON

  • 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 package.
  • conan_package_reference - The unique Conan package ID reference.
  • package_metadata - Additional metadata about the Conan package retrieved from GitLab.

Dependencies

  • GitLab API authentication token or credentials

Troubleshooting

  • Ensure all required path parameters (package_name, package_version, package_username, package_channel, conan_package_reference) are correctly provided and not empty.
  • If authentication is enabled, verify that the GitLab API credentials are valid and have the necessary permissions to access the package registry.
  • Check the baseUrl if using a self-hosted GitLab instance to ensure it is correct.
  • Common error messages may include 401 Unauthorized (authentication issues), 404 Not Found (incorrect package details), or 400 Bad Request (invalid parameters).

Links

Discussion