Bitbucket Data CenterInstall

Overview

This node interacts with the Bitbucket Data Center API to manage tags within repositories. Specifically, the "Delete" operation for the "Tag" resource allows users to delete a tag from a specified repository in a project. This is useful for cleaning up obsolete or incorrect tags in your version control system.

Common scenarios include:

• Removing outdated release tags.
• Deleting mistakenly created tags.
• Automating tag management as part of CI/CD pipelines.

Example: Automatically delete a tag named "v1.0.0" from a repository after a rollback event.

Properties

Output

The output JSON contains an object indicating success of the deletion operation:

{
  "success": true
}

If the deletion is successful, the success field will be true. If there is an error, the node will throw an error unless configured to continue on failure, in which case the error message will be included in the output.

No binary data is output by this operation.

Dependencies

• Requires access to a Bitbucket Data Center server.
• Requires credentials for authentication, either a personal access token or basic authentication.
• The node expects the user to specify the project key and repository slug (not shown in the provided properties but required by the API call).
• Proper permissions on the Bitbucket server to delete tags.

Troubleshooting

• Common issues:

  • Incorrect or missing project key or repository slug parameters will cause the API call to fail.
  • Insufficient permissions to delete tags will result in authorization errors.
  • Providing a non-existent tag name will likely return a not found error.
  • Network or server connectivity issues can cause request failures.

• Error messages:

  • "Bitbucket Data Center API request failed: <message>": Indicates an issue with the API request; check credentials, URL, and network.
  • "The operation "delete" is not supported for resource "tag": Should not occur if using the correct operation; indicates misconfiguration.
  • Other HTTP errors from the Bitbucket API should be interpreted according to their status codes (e.g., 403 Forbidden, 404 Not Found).

• Resolution tips:

  • Verify that the project key and repository slug are correctly set.
  • Ensure the tag name exists in the repository.
  • Confirm that the authentication credentials have sufficient rights.
  • Enable "Continue On Fail" in the node settings to handle errors gracefully during batch operations.

Links and References

• Bitbucket Data Center REST API Documentation - Tags
• Bitbucket Server API - Delete Tag
• n8n Documentation: Creating Custom Nodes