GitLab API

GitlabTool
Join our community

Actions905

Overview

This node operation retrieves a specific Conan package from the GitLab Packages Conan API (v1) using detailed path parameters. It is useful for users who want to fetch metadata or details about a particular Conan package version hosted on GitLab. For example, developers managing C++ package dependencies can use this node to programmatically access package information for automation or integration workflows.

Use Case Examples

  1. Fetch details of a Conan package named 'my-package' version '1.0' under the user 'my-group+my-project' and channel 'stable' with a specific Conan package reference ID.
  2. Automate retrieval of package metadata for continuous integration pipelines that depend on specific Conan packages hosted on GitLab.

Properties

Name Meaning
Skip Authentication Option to skip authentication when making the API request.
Authentication Type of authentication to use for the API request, defaulting to GitLab API key authentication.
baseUrl Base URL of the GitLab instance to which the API request is sent, defaulting to https://gitlab.com.
Method HTTP method used for the API request, defaulting to GET.
Path Parameters Collection of path parameters required to specify the Conan package uniquely in the API request.

Output

JSON

  • id - Unique identifier of the Conan package.
  • name - Name of the Conan package.
  • version - Version of the Conan package.
  • username - Username or group/project owning the package.
  • channel - Channel of the Conan package.
  • reference - Conan package reference ID.
  • metadata - Additional metadata or details about the Conan package.

Dependencies

  • GitLab API key credential for authentication

Troubleshooting

  • Ensure all required path parameters (package_name, package_version, package_username, package_channel, conan_package_reference) are provided and correctly formatted.
  • If authentication is enabled, verify that the GitLab API key credential is valid and has sufficient permissions to access the package.
  • Check the baseUrl if using a self-hosted GitLab instance to ensure it is correct.
  • Common error messages may include 404 Not Found if the package does not exist or 401 Unauthorized if authentication fails.

Links

Discussion