GitLab API

GitlabTool
Join our community

Actions1000

Overview

This node operation retrieves a specific Debian package file from a GitLab group repository using detailed parameters such as group ID, Debian distribution, component, architecture, and the SHA256 hash of the file. It is useful for automating the fetching of Debian package files in CI/CD pipelines or package management workflows within GitLab.

Use Case Examples

  1. Fetch a Debian installer binary package for a specific architecture and component from a GitLab group by providing the group ID, distribution codename, component name, architecture type, and the SHA256 hash of the file.
  2. Automate the retrieval of Debian package files for deployment or analysis by specifying the exact package details through the node's input properties.

Properties

Name Meaning
Skip Authentication Option to skip authentication when making 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 Query parameters for the API request, specifically the Debian distribution codename or suite.
Path Parameters Path parameters for the API request including group ID, Debian component, architecture, and the SHA256 hash of the file.

Output

JSON

  • id - The group ID or full group path used in the request.
  • distribution - The Debian Codename or Suite specified in the query parameters.
  • component - The Debian Component specified in the path parameters.
  • architecture - The Debian Architecture specified in the path parameters.
  • file_sha256 - The SHA256 hash of the file specified in the path parameters.

Dependencies

  • GitLab API key credential

Troubleshooting

  • Ensure all required path and query parameters are correctly provided and formatted, especially the SHA256 hash which must be accurate.
  • If authentication is enabled, verify that the GitLab API key credential is valid and has sufficient permissions to access the group and package data.
  • Check the base URL to ensure it points to the correct GitLab instance if using a self-hosted GitLab server.

Links

Discussion