Actions50
- Branch Actions
- Commit Actions
- Issue Actions
- Project Actions
- Pull Request Actions
- Repository Actions
- Tag Actions
- File Actions
- User Actions
- Webhook Actions
Overview
This node allows you to create a tag in a Bitbucket Data Center repository. Tagging is useful for marking specific points in your repository's history, such as releases or important commits. By creating tags, you can easily reference these points later, facilitating version control and deployment processes.
Typical use cases include:
- Marking release versions (e.g., v1.0, v2.0) in your codebase.
- Creating tags from specific branches or commit hashes to snapshot the state of the repository.
- Adding optional messages to tags to provide context or notes about the tagged point.
For example, you might create a tag named "release-2024-06" starting from the "main" branch with a message describing the release details.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate API requests: either "Personal Access Token" or "Basic Auth". |
| Tag Name | The name of the tag to create. |
| Start Point | The commit hash or branch name from which the tag will be created (e.g., "main"). |
| Tag Message | Optional message describing the tag. |
Output
The node outputs JSON data representing the created tag object returned by the Bitbucket Data Center API. This typically includes details such as the tag name, start point, message, and metadata about the tag creation.
No binary data output is produced by this operation.
Dependencies
- Requires access to a Bitbucket Data Center instance.
- Requires authentication via either a personal access token or basic authentication credentials.
- The node expects the user to configure credentials that provide access to the Bitbucket Data Center API server URL and authentication tokens.
Troubleshooting
- Authentication errors: Ensure that the provided API key or basic auth credentials are valid and have sufficient permissions to create tags in the target repository.
- Invalid start point: The "Start Point" must be a valid commit hash or branch name existing in the repository; otherwise, the API will reject the request.
- Tag name conflicts: Attempting to create a tag with a name that already exists may result in an error. Use unique tag names.
- API request failures: Network issues or incorrect server URLs can cause request failures. Verify connectivity and correct server configuration.
Common error messages include:
"Bitbucket Data Center API request failed: <error message>"ā indicates an issue with the API call; check credentials, parameters, and network."The operation "create" is not supported for resource "tag"ā would indicate misuse of the node but should not occur if configured correctly.