GitLab API

GitlabTool
Join our community

Actions1000

Overview

This node operation interacts with the GitLab API to generate upload URLs for a specific Conan package version. It is useful for automating the process of uploading package files to GitLab's Conan package registry. Typical use cases include CI/CD pipelines where package uploads need to be managed programmatically, or integration workflows that handle package distribution.

Use Case Examples

  1. Uploading a new version of a Conan package to GitLab's package registry by obtaining the necessary upload URLs.
  2. Automating package management in a DevOps pipeline by dynamically generating upload URLs for package files.

Properties

Name Meaning
Skip Authentication Determines whether to skip authentication for the API request.
Authentication Specifies the authentication method to use, typically an API key credential for GitLab.
baseUrl The base URL of the GitLab instance to which the request is sent.
Method The HTTP method used for the request, defaulting to GET but can be set to POST, PUT, DELETE, HEAD, or PATCH.
Path Parameters Parameters required in the API path to specify the Conan package details, including package name, version, username, and channel.

Output

JSON

  • upload_urls - The URLs generated for uploading the Conan package files.

Dependencies

  • GitLab API key credential

Troubleshooting

  • Ensure the path parameters (package_name, package_version, package_username, package_channel) are correctly set and match the package details in GitLab.
  • Verify that the GitLab API key credential is valid and has the necessary 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 authentication failures, 404 not found if the package details are incorrect, or permission denied errors. Verify credentials and package existence to resolve these.

Links

Discussion