GitLab API icon

GitLab API

Gitlab
Join our community

Actions917

Overview

This node operation uploads a Maven package file to a specific project in GitLab using the GitLab API. It is useful for automating the deployment of Maven artifacts to GitLab's package registry, enabling continuous integration and delivery workflows for Java projects.

Use Case Examples

  1. Uploading a Maven POM file to a GitLab project to publish a new package version.
  2. Automating the deployment of Maven artifacts as part of a CI/CD pipeline.

Properties

Name Meaning
Skip Authentication If true, the node will skip using authentication for the request.
Authentication The authentication method used for the request, typically an API key credential for GitLab.
baseUrl The base URL of the GitLab instance, defaulting to https://gitlab.com.
Method The HTTP method to use for the request, default is PUT for this operation.
Path Parameters Parameters used in the request path to specify the project ID and the Maven package file name.

Output

JSON

  • response - The JSON response from the GitLab API after uploading the Maven package file.

Dependencies

  • Requires GitLab API authentication credentials (API key or token).

Troubleshooting

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

Links

Discussion