GitLab API

GitlabTool
Join our community

Actions1000

Overview

This node operation updates the TeamCity integration settings for a specific GitLab project by sending a PUT request to the GitLab API endpoint `/api/v4/projects/{id}/integrations/teamcity`. It is useful for automating the configuration of TeamCity CI/CD integration within GitLab projects, enabling seamless continuous integration workflows.

Use Case Examples

  1. Automatically update TeamCity integration settings for a project when project details change.
  2. Enable or disable TeamCity integration for multiple projects in bulk via automation.

Properties

Name Meaning
Skip Authentication Determines whether to skip authentication for the API request.
Authentication Specifies the authentication method to use for the API request, defaulting to GitLab API key authentication.
baseUrl The base URL of the GitLab instance to which the API request is sent.
Method The HTTP method used for the API request, defaulting to PUT for this operation.
Path Parameters The path parameters for the API request, specifically the project ID to identify which project's TeamCity integration to update.

Output

JSON

  • id - The ID of the GitLab project.
  • teamcity_integration_status - The status or details of the TeamCity integration after the update.

Dependencies

  • GitLab API key credential

Troubleshooting

  • Ensure the project ID provided in the path parameters is valid and exists in the GitLab instance.
  • Verify that the API key used for authentication has sufficient permissions to update project integrations.
  • Check the base URL to confirm it points to the correct GitLab instance, especially if using a self-hosted GitLab server.
  • If skipping authentication, ensure the API endpoint allows unauthenticated requests, otherwise the request will fail.

Links

Discussion