GitLab API

GitlabTool

Actions1000

Overview

This node operation retrieves a specific Conan package from GitLab's package registry using the GitLab API. It is useful for users who want to fetch detailed information about a Conan package by specifying its name, version, username, and channel. Practical examples include automating package retrieval in CI/CD pipelines or integrating package data into other workflows.

Use Case Examples

  1. Fetch a Conan package named 'my-package' with version '1.0' for user 'my-group+my-project' on the 'stable' channel from GitLab.
  2. Automate the retrieval of Conan package details to verify package versions before deployment.

Properties

Name Meaning
Skip Authentication Option to skip authentication when making the API request.
baseUrl The base URL of the GitLab instance to send the API request to.
Method HTTP method to use for the API request (GET, POST, PUT, DELETE, HEAD, PATCH).
Path Parameters Parameters required in the API request path to specify the Conan package details.

Output

JSON

  • package_name - The name of the retrieved Conan package.
  • package_version - The version of the retrieved Conan package.
  • package_username - The username or group/project owning the retrieved package.
  • package_channel - The channel of the retrieved Conan package.
  • package_data - Detailed data about the Conan package returned by the GitLab API.

Dependencies

  • GitLab API authentication token or credentials

Troubleshooting

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

Links

Discussion