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 interacts with the Bitbucket Data Center API to perform various operations on commits within a specified project and repository. Specifically, for the "Commit" resource with the "Get All" operation, it retrieves a list of commits from a given repository in a project. This is useful for scenarios where you want to analyze commit history, audit changes, or trigger workflows based on recent commits.
Practical examples include:
- Fetching all commits from a repository to generate reports or changelogs.
- Monitoring commit activity for continuous integration or deployment pipelines.
- Integrating commit data into other tools like issue trackers or notification systems.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication: "Personal Access Token" or "Basic Auth". |
| Project | The key of the project containing the repository to query. |
| Return All | Whether to return all commits or limit the number of results. |
| Limit | Maximum number of commits to return (applicable if "Return All" is false). Range 1-500. |
Output
The output is a JSON array where each element represents a commit object retrieved from the Bitbucket Data Center API. Each commit object contains detailed information about the commit such as its ID, author, message, timestamp, and other metadata as provided by the API.
No binary data output is produced by this operation.
Dependencies
- Requires access to a Bitbucket Data Center instance.
- Requires either a Personal Access Token or Basic Authentication credentials configured in n8n.
- The node uses the Bitbucket Data Center REST API endpoints under
/rest/api/1.0/projects/{projectKey}/repos/{repositorySlug}/commits.
Troubleshooting
- Authentication errors: Ensure that the provided credentials (Personal Access Token or Basic Auth) are valid and have sufficient permissions to access the project and repository.
- Project or Repository not found: Verify that the selected project key and repository slug exist and are accessible by the authenticated user.
- Limit exceeded: The API limits the maximum number of commits returned per request; use the "Return All" option to fetch all commits or adjust the "Limit" accordingly.
- API request failures: Network issues or incorrect server URLs can cause request failures. Check the Bitbucket server URL configuration and network connectivity.
- Unsupported operations: Using an operation not supported for the "commit" resource will throw an error.
Error messages typically start with Bitbucket Data Center API request failed: followed by the specific reason. Review the message to identify issues such as permission denied, resource not found, or invalid parameters.