GitLab API icon

GitLab API

Gitlab
Join our community

Actions880

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 desired 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.
baseUrl The base URL of the GitLab instance to connect to, defaulting to https://gitlab.com.
Method HTTP method to use for the API request, default is GET with options including POST, PUT, DELETE, HEAD, PATCH.
Query Parameters Parameters sent in the query string of the API request, specifically the Debian distribution codename or suite.
Path Parameters Parameters included in the API request path, including group ID or full group path, Debian component, architecture, and the SHA256 hash of the file to retrieve.

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 authentication token or credentials

Troubleshooting

  • Ensure all required path parameters (id, component, architecture, file_sha256) and query parameter (distribution) are correctly provided and formatted.
  • If authentication is enabled, verify that the GitLab API credentials are valid and have sufficient permissions to access the group and package data.
  • Check the baseUrl if connecting to a self-hosted GitLab instance to ensure it is correct.
  • Common error messages may include 404 Not Found if the specified package or group does not exist, or 401 Unauthorized if authentication fails.

Discussion