Bitbucket Data Center icon

Bitbucket Data Center

Interact with Bitbucket Data Center API
Join our community

Actions50

Overview

The node interacts with the Bitbucket Data Center API to manage repositories within projects. Specifically, the Update Repository operation allows users to modify repository details such as its name, description, and visibility (public or private). This is useful for maintaining accurate metadata about repositories, reflecting changes in project structure, or adjusting access settings.

Typical use cases include:

  • Renaming a repository after a rebranding or restructuring.
  • Updating the repository description to provide clearer information to collaborators.
  • Changing the repository's visibility status to control public access.

For example, a user might update a repository named "my-repo" under project "PROJ" to change its description to "Updated repo for new features" and make it public.

Properties

Name Meaning
Authentication Method of authentication: either "Personal Access Token" or "Basic Auth".
Project The key of the project containing the repository to update.
Repository The slug identifier of the repository to update.
Description New description text for the repository.
Repository Name New name for the repository.
Public Boolean flag indicating whether the repository should be public (true) or private (false).

Output

The output is a JSON object representing the updated repository resource as returned by the Bitbucket Data Center API. It typically includes fields such as repository ID, name, slug, description, public status, project details, and other metadata.

If the update operation succeeds, the node returns the updated repository data. If an error occurs, the node throws an error unless configured to continue on failure, in which case it outputs an error message object.

No binary data output is involved in this operation.

Dependencies

  • Requires access to a Bitbucket Data Center instance with appropriate API permissions.
  • Requires credentials for authentication, either via a personal access token or basic authentication.
  • The node expects the Bitbucket server URL to be configured in the credentials.
  • Uses n8n's built-in HTTP request helper with authentication support.

Troubleshooting

  • Common issues:

    • Invalid project key or repository slug: Ensure the project and repository exist and are correctly specified.
    • Insufficient permissions: The API credentials must have rights to update repository details.
    • Network or connectivity problems to the Bitbucket server.

  • Error messages:

    • "Bitbucket Data Center API request failed: <message>" indicates an issue with the API call; check credentials, URL, and network.
    • "The operation "update" is not supported for resource "repository" would indicate a misconfiguration or unsupported operation, but this should not occur for the Update operation.

  • To resolve errors, verify credentials, project and repository identifiers, and ensure the Bitbucket server is reachable.

Links and References

Discussion