GitLab API

GitlabTool

Actions905

Overview

This node interacts with the GitLab API to create a new asset link for a specific release in a GitLab project. It is useful for automating the management of release assets, such as adding downloadable links to release notes. For example, it can be used in CI/CD pipelines to automatically attach build artifacts or documentation links to a release tag.

Use Case Examples

  1. Automatically add a download link to a release asset after a successful build.
  2. Manage release assets by programmatically adding or updating links associated with a release tag in a GitLab project.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the request.
Authentication Type of authentication used, defaulting to GitLab API key authentication.
baseUrl Base URL of the GitLab instance, default is https://gitlab.com.
Method HTTP method to use for the request, default is GET.
Parameter Schema Defines the required path parameters and request body schema for the operation postApiV4ProjectsIdReleasesTagNameAssetsLinks.
Request Body Schema Schema for the request body, specific to the operation postApiV4ProjectsIdReleasesTagNameAssetsLinks.
Request Path API endpoint path for creating asset links on a release.
Path Parameters Collection of path parameters including project ID and release tag name required for the API call.

Output

JSON

  • response - The JSON response from the GitLab API after creating the asset link.

Dependencies

  • GitLab API key credential

Troubleshooting

  • Ensure the project ID and tag name are correctly specified and URL-encoded if necessary.
  • Verify that the authentication credentials are valid and have sufficient permissions to modify releases.
  • Check the base URL if using a self-hosted GitLab instance to ensure it is correct.
  • Common errors include 401 Unauthorized (invalid or missing credentials), 404 Not Found (incorrect project ID or tag name), and 400 Bad Request (invalid request body).

Links

Discussion