GitLab API icon

GitLab API

Gitlab

Actions917

Overview

This node operation retrieves a specific Conan package from a GitLab project using the GitLab API. It is useful for automating the process of fetching package details in CI/CD pipelines or package management workflows within GitLab projects. For example, it can be used to get metadata or contents of a Conan package version identified by project ID, package name, version, username, and channel.

Use Case Examples

  1. Fetch a Conan package version '1.0' named 'my-package' from a project with ID '123' for user 'my-group+my-project' on the 'stable' channel.
  2. Automate retrieval of Conan package details during a build process to ensure dependencies are up to date.

Properties

Name Meaning
Skip Authentication Whether to skip authentication for the request (boolean). Defaults to false.
Authentication Type of authentication used, hidden unless Skip Authentication is false. Defaults to GitLab API key.
baseUrl Base URL of the GitLab instance. Defaults to https://gitlab.com.
Method HTTP method to use for the request. Defaults to GET.
Path Parameters Collection of path parameters required to identify the Conan package in the GitLab project.

Output

JSON

  • id - The ID or URL-encoded path of the project.
  • package_name - Name of the Conan package.
  • package_version - Version of the Conan package.
  • package_username - Username or group owning the package.
  • package_channel - Channel of the Conan package.
  • package_details - Details of the retrieved Conan package from the GitLab API.

Dependencies

  • GitLab API key credential for authentication unless Skip Authentication is true

Troubleshooting

  • Ensure all required path parameters (id, package_name, package_version, package_username, package_channel) 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 project and packages.
  • Check the baseUrl if using a self-hosted GitLab instance to ensure it is correct.
  • Common errors include 404 Not Found if the package or project does not exist, and 401 Unauthorized if authentication fails.

Links

Discussion