GitLab API

GitlabTool
Join our community

Actions1000

Overview

This node operation updates the TeamCity service integration settings for a specific GitLab project. It is useful for automating the configuration of TeamCity CI/CD integration within GitLab projects, allowing users to programmatically manage their project services without manual intervention. For example, a DevOps engineer can use this node to enable or modify TeamCity integration settings across multiple projects in a GitLab instance.

Use Case Examples

  1. Updating TeamCity service settings for a GitLab project with ID 12345 to enable or configure build triggers.
  2. Automating the setup of TeamCity integration for new projects created in GitLab.

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 GET but can be set to PUT for this operation.
Path Parameters Parameters included in the request path, specifically the project ID to identify which project's TeamCity service to update.

Output

JSON

  • id - The ID of the GitLab project for which the TeamCity service integration was updated.
  • service_status - The status or result of the TeamCity service update operation.

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

Links

Discussion