GitLab API icon

GitLab API

Gitlab
Join our community

Actions880

Overview

This node operation retrieves a specific Conan package from a GitLab project using the GitLab API. It is useful for users who want to fetch detailed information about a Conan package version stored in a GitLab project's package registry. For example, developers managing C++ package dependencies can use this node to programmatically access package metadata or verify package versions.

Use Case Examples

  1. Fetch details of a Conan package named 'my-package' version '1.0' from a GitLab project identified by its ID or URL-encoded path.
  2. Retrieve package information for a Conan package with a specific username and channel, such as 'my-group+my-project' and 'stable'.
  3. Automate the process of checking package versions in CI/CD pipelines by integrating this node to query GitLab's package registry.

Properties

Name Meaning
Skip Authentication Whether to skip authentication when making the API request.
baseUrl The base URL of the GitLab instance to which the API request is sent.
Method The HTTP method used for the API request (GET, POST, PUT, DELETE, HEAD, PATCH).
Path Parameters Parameters used to construct the API request path, including project ID, package name, version, username, and channel.

Output

JSON

  • id - The ID or URL-encoded path of the GitLab project.
  • package_name - The name of the Conan package.
  • package_version - The version of the Conan package.
  • package_username - The username associated with the Conan package.
  • package_channel - The channel of the Conan package.
  • response - The JSON response from the GitLab API containing the package details.

Dependencies

  • GitLab API authentication token or credentials

Troubleshooting

  • Ensure the project ID and package parameters are correctly URL-encoded to avoid 404 errors.
  • Verify that the GitLab API credentials are valid and have sufficient permissions to access the project's package registry.
  • Check the base URL if using a self-hosted GitLab instance to ensure the API endpoint is reachable.
  • Common error messages include 401 Unauthorized (invalid or missing credentials) and 404 Not Found (incorrect project or package details).

Links

Discussion