ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #bitbucket
Pull Request Date Conversion When automating pull request creation via the Bitbucket REST API (v2), the system requires date/time values to adhere strictly to the ISO 8601 format. A common failure occurs when a timestamp is provided without an explicit timezone offset, triggering a 400 Bad Request error. While Bitbucket stores timestamps internally in UTC an
Goal: Assess whether enabling the automatic repository archiving feature (introduced in Bitbucket Cloud 8.12) will lower storage expenses for repositories with infrequent activity while preserving required read‑only access. Archived repositories become read‑only, blocking pushes, pull requests and Pipelines execution. Storage is billed at a reduced rate, but
In Bitbucket Pipelines, cancelling a step or exceeding its timeout triggers an immediate shutdown: a SIGTERM is sent, followed by a SIGKILL after a fixed ~10‑second interval. The runner does not expose any setting to adjust that interval, nor does it provide a hook for pre‑stop cleanup. Consequently, applications that rely on graceful shutdown—such as those
Bitbucket Cloud allows repository administrators and workspace owners to toggle repository visibility between private and public via the user interface or REST API. While these actions are critical security events, the current permission model lacks granular controls to restrict this specific action from certain administrators. The standard audit log does no
Accessibility gap in pull-request merge control The merge button in Bitbucket Cloud pull requests does not expose an explicit aria-disabled attribute when the button enters a disabled state. Screen readers therefore announce the control inconsistently—some read it as an ordinary button, others as unavailable—leaving users uncertain whether the action is trul
Pull Request Approval Enforcement Bitbucket Cloud allows administrators to define merge checks that require a minimum number of reviewer approvals before a pull request can be merged into a protected branch. This mechanism ensures that code changes undergo a mandatory peer review process. When combining these merge checks with project-level permission inheri
I need to decide the safe recovery path after a Bitbucket upgrade fails before completing the upgrade wizard. The goal is to avoid starting the application against a partially migrated database or mixed-version cluster nodes. Bitbucket does not automatically roll back a failed upgrade, and database schema changes are not officially reversible. The upgrade lo
When integrating external automation with the Bitbucket Server/Data Center REST API, network timeouts during POST requests create uncertainty regarding whether a resource was successfully created on the server before the connection dropped. Because standard write endpoints for entities like pull requests or repositories do not natively support idempotency ke
Decision goal Select a documented Bitbucket Server Docker image for CI pipelines that requires a predictable Java runtime and stable webhook and permission behavior across upgrades. Constraints and uncertainty Bitbucket Server 8.x and later require Java 11, while 5.x-7.x run on Java 8. Branch permission schemes introduced in 8.0 are not backward-compatible w