GiteaInstall

Overview

This node interacts with a Gitea instance via its API to retrieve a runner registration token for a specific repository. This token is typically used to register self-hosted runners that can execute CI/CD workflows on the repository.

Common scenarios include:

• Automating the setup of self-hosted runners for repositories.
• Integrating runner management into DevOps pipelines.
• Dynamically fetching tokens for secure runner registration without manual intervention.

For example, a user might use this node to programmatically obtain a registration token each time a new runner needs to be added to a repository's CI/CD environment.

Properties

Output

The node outputs JSON data containing the runner registration token associated with the specified repository. This token is used to authenticate and register self-hosted runners with the repository's CI/CD system.

No binary data output is involved.

Dependencies

• Requires an active connection to a Gitea instance.
• Needs an API authentication credential configured in n8n to authorize requests against the Gitea API.
• The base URL of the Gitea server must be provided in the credentials configuration.

Troubleshooting

• Invalid Owner or Repo: If the owner or repository name is incorrect or does not exist, the API will return an error. Verify the spelling and existence of the repository.
• Authentication Errors: Missing or invalid API credentials will cause authorization failures. Ensure the API key/token is valid and has sufficient permissions.
• Network Issues: Connectivity problems to the Gitea server will prevent the node from retrieving the token. Check network access and server availability.
• API Changes: If the Gitea API version changes, the endpoint or response format might differ, causing errors. Confirm compatibility with the Gitea version in use.

Links and References

• Gitea API Documentation
• Self-hosted Runners in Gitea
• n8n Documentation