GitLab API icon

GitLab API

Gitlab
Join our community

Actions917

Overview

This node operation interacts with the GitLab API to upload Conan package upload URLs for a specific project. It is designed to facilitate the management of Conan packages within GitLab projects by allowing users to specify detailed package information such as project ID, package name, version, username, channel, and package reference. This operation is useful for automating package uploads in CI/CD pipelines or package management workflows.

Use Case Examples

  1. Uploading Conan package URLs for a project to automate package distribution.
  2. Integrating Conan package management into GitLab CI/CD pipelines for continuous deployment.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the API request.
Authentication Type of authentication used for the API request, hidden unless Skip Authentication is false.
baseUrl Base URL for the GitLab instance, defaulting to https://gitlab.com.
Method HTTP method to use for the API request, default is GET but POST is used for this operation.
Parameter Schema Defines required path parameters for the API call including project ID, package name, version, username, channel, and Conan package reference.
Request Body Schema Schema for the request body, not specified (null) for this operation.
Request Path API endpoint path template for uploading Conan package URLs.
Path Parameters Collection of path parameters required to construct the API request URL, including project ID, package name, version, username, channel, and Conan package reference.

Output

JSON

  • upload_urls - The URLs returned by the API for uploading the Conan package files.

Dependencies

  • GitLab API authentication token or credentials

Troubleshooting

  • Ensure all required path parameters are correctly provided and URL-encoded if necessary.
  • Verify that the GitLab API credentials are valid and have sufficient permissions to access the project and manage packages.
  • Check the baseUrl if using a self-hosted GitLab instance to ensure it is correct.
  • Common error messages may include 401 Unauthorized (authentication issues), 404 Not Found (incorrect project or package details), or 400 Bad Request (invalid parameters). Resolving these involves verifying credentials, parameters, and API endpoint correctness.

Links

Discussion