GitLab API

GitlabTool
Join our community

Actions905

Overview

This node operation fetches the latest release information of a specified GitLab project using the GitLab API v4. It allows users to retrieve details about the most recent release and optionally append a suffix path to the permalink URL of that release. This is useful for automation workflows that need to track or utilize the latest release data of a project, such as deployment pipelines, release monitoring, or integration with other tools.

Use Case Examples

  1. Retrieve the latest release details of a project by its ID or URL-encoded path.
  2. Fetch the latest release permalink and append a custom suffix path for accessing specific assets or files related to the release.

Properties

Name Meaning
Skip Authentication Whether to skip authentication for the API request.
Authentication The authentication method used for the API request, defaulting to GitLab API key authentication.
baseUrl The base URL of the GitLab instance, defaulting to https://gitlab.com.
Method The HTTP method used for the API request, defaulting to GET.
Query Parameters.suffix_path The path to be suffixed to the latest release permalink URL, allowing access to specific sub-resources or files.
Path Parameters.id The ID or URL-encoded path of the GitLab project whose latest release is being fetched.

Output

JSON

  • id - The unique identifier of the release.
  • tag_name - The tag name associated with the release.
  • name - The name of the release.
  • description - The description or notes of the release.
  • created_at - The creation timestamp of the release.
  • released_at - The release timestamp.
  • author - Information about the author of the release.
  • assets - Assets associated with the release, such as links to binaries or source code.
  • commit - The commit associated with the release.

Dependencies

  • GitLab API key credential

Troubleshooting

  • Ensure the project ID or URL-encoded path is correct to avoid 404 Not Found errors.
  • Verify that the API key credential is valid and has sufficient permissions to access the project's release information.
  • If using a custom base URL, ensure it points to a valid GitLab instance and the API endpoint is accessible.
  • Check that the suffix_path query parameter is correctly formatted if used, as an invalid path may cause errors or unexpected results.

Links

Discussion