GitLab API

GitlabTool
Join our community

Actions905

Overview

This node operation allows users to post evidence for a specific release associated with a Git tag in a GitLab project. It is useful for adding proof or documentation to a release, such as build artifacts or verification files, enhancing release traceability and compliance.

Use Case Examples

  1. A developer wants to attach a security scan report as evidence to a release tagged 'v1.0' in their GitLab project with ID 123.
  2. A release manager needs to upload compliance documentation as evidence for a specific release before deployment.

Properties

Name Meaning
Skip Authentication Whether to skip authentication for the API request.
Authentication The authentication method used for the API request, 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 POST for this operation.
Path Parameters Parameters required in the request path to identify the project and release tag.

Output

JSON

  • response - The JSON response from the GitLab API confirming the evidence was posted or details of the evidence.

Dependencies

  • GitLab API authentication token or API key credential

Troubleshooting

  • Ensure the project ID and tag name are correct and exist in the GitLab instance.
  • Verify that the authentication token has sufficient permissions to post release evidence.
  • Check the base URL to confirm it points to the correct GitLab instance, especially if using a self-hosted GitLab.
  • Common error messages include 404 Not Found if the project or tag does not exist, and 401 Unauthorized if authentication fails.

Links

Discussion