Preventing Production Accidents with Bitbucket Branch Permissions
Stop accidental production pushes by leveraging Bitbucket Branch Permissions and Merge Checks. Learn how to enforce PR workflows and choose the right merge strategy for your team.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Stop accidental production pushes by leveraging Bitbucket Branch Permissions and Merge Checks. Learn how to enforce PR workflows and choose the right merge strategy for your team.
Learn how to select the right Bitbucket Pipelines cache for Java Maven builds, compare Docker layer, artifact, and custom script caches, and implement the artifact cache to reduce dependency download time.
Our team maintains a Bitbucket repository that uses a self‑hosted runner to build Docker images and push them to an internal container registry. The pipeline step that executes docker push consistently fails with a "permission denied" message, even though the registry URL, repository name, and tag are correct. We have stored the registry username and passwor
What are the recommended steps to upgrade a Bitbucket Server or Data Center deployment while ensuring a reliable rollback path if issues arise? Please outline the preparation, backup, upgrade execution, verification, and rollback procedures, highlighting any assumptions about environment (e.g., supported versions, database compatibility) and noting where off
Bitbucket Data Center ties supported Java major version to specific product releases. The supported range changes across major and minor versions, so a supported deployment requires a documented pairing of Data Center release and Java runtime. Upgrading across Java major versions is constrained by release-specific support boundaries and by plugin and third-p
Bitbucket Cloud Webhook Reliability Integrating Bitbucket Cloud with external monitoring tools requires reliable event delivery via webhooks. When a destination endpoint returns a non-2xx HTTP response code, the system logs the delivery failure. However, there is uncertainty regarding the consistency of automatic retry logic across different event types duri
In Bitbucket Data Center 8.5, a pull request can continue to display an approval from a user who has been removed from the reviewers group. The goal is to make the approval list reflect current group membership immediately, without waiting for the cached entry to expire. The reviewer-approval cache is keyed to group membership at request time, and no configu
Bitbucket Server utilizes HikariCP for JDBC connection pooling, with a default maximum-pool-size of 10. The pool manages connection lifecycles through background eviction and idle timeouts to ensure resource efficiency. A potential conflict arises when the database server's own idle timeout is configured to be shorter than the application's eviction interval
Fast‑Forward and Merge Commit are the two primary merge strategies available in Bitbucket. The choice directly influences how a repository’s commit graph appears, how teams can trace feature integration, and how clean the branch history remains. Fast‑Forward keeps the graph linear, reduces merge commits, and simplifies bisect operations, but it can hide the