GitLab API

GitlabTool
Join our community

Actions1000

Overview

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

Use Case Examples

  1. Automatically update TeamCity integration settings for a GitLab group as part of a CI/CD pipeline.
  2. Manage multiple GitLab group integrations programmatically to ensure consistent TeamCity configuration across projects.

Properties

Name Meaning
Skip Authentication Determines whether to skip authentication for the API request.
Authentication Specifies the authentication method to use, 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 request, default is GET but for this operation it should be PUT.
Path Parameters Parameters included in the request path, specifically the group ID to identify which group's TeamCity integration to update.

Output

JSON

  • id - The ID of the GitLab group for which the TeamCity integration is updated.
  • integrationStatus - Status or response details of the TeamCity integration update operation.

Dependencies

  • GitLab API key credential

Troubleshooting

  • Ensure the group 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 group integrations.
  • Check the base URL to confirm it points to the correct GitLab instance.
  • If skipping authentication, ensure the API endpoint allows unauthenticated requests, otherwise the request will fail.

Links

Discussion