Gitea icon

Gitea

Interact with Gitea via API
Join our community

Actions393

Overview

This node interacts with the Gitea API to retrieve a runner registration token for a specified organization. This token is typically used to register self-hosted runners in continuous integration workflows, allowing them to connect securely to the organization's repositories and perform automated tasks such as builds or tests.

Common scenarios include:

  • Automating the setup of CI/CD pipelines by programmatically obtaining runner tokens.
  • Managing multiple organizations' runners in an automated fashion.
  • Integrating with infrastructure-as-code tools to provision runners dynamically.

Example: A DevOps engineer can use this node to fetch the registration token for their organization's runners and then use that token to configure new runner instances without manual intervention.

Properties

Name Meaning
Org The name of the organization for which to retrieve the runner registration token.

Output

The node outputs JSON data containing the runner registration token associated with the specified organization. This token is essential for registering new runners with the organization's CI system.

If the node supports binary data output (not evident from the provided code), it would typically relate to any files or certificates needed for runner registration, but no such indication is present here.

Dependencies

  • Requires an API key credential to authenticate with the Gitea instance.
  • Needs the base URL of the Gitea server configured in the credentials.
  • Depends on the Gitea REST API endpoint /api/v1 to fetch the runner registration token.

Troubleshooting

  • Invalid Organization Name: If the organization name is incorrect or does not exist, the API will likely return an error indicating the resource was not found. Verify the organization name spelling and existence.
  • Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key is valid and has sufficient permissions.
  • Network Issues: Connectivity problems to the Gitea server will prevent token retrieval. 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 current Gitea API version.

Links and References

Discussion