GitLab API

GitlabTool

Actions905

Overview

This node operation retrieves a specific Conan package from the GitLab API using the package's name, version, username, and channel. It is useful for automating the fetching of package details in CI/CD pipelines or package management workflows within GitLab projects.

Use Case Examples

  1. Fetch details of a Conan package named 'my-package' version '1.0' for user 'my-group+my-project' on the 'stable' channel.
  2. Automate retrieval of package metadata for dependency management in a build process.

Properties

Name Meaning
Skip Authentication Determines whether to skip authentication when making the API request.
Authentication Specifies the authentication method to use, defaulting to GitLab API credentials if not skipped.
baseUrl The base URL of the GitLab instance to which the API request is sent, defaulting to https://gitlab.com.
Method The HTTP method used for the API request, defaulting to GET.
Path Parameters Collection of parameters required in the API path to identify the Conan package: package_name, package_version, package_username, and package_channel.

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 associated with the package.
  • channel - Channel of the package, such as stable or testing.
  • metadata - Additional metadata about the package returned by the GitLab API.

Dependencies

  • GitLab API credentials for authentication

Troubleshooting

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

Links

Discussion