Bitbucket Data Center webhooks to Bamboo Data Center: concurrent push handling and latency

The goal is to determine the documented behavior of Bamboo Data Center when receiving multiple rapid push webhooks from Bitbucket Data Center. Because Bamboo Data Center persists build metadata via Hibernate/JPA to a shared relational database, concurrent plan executions can increase contention on build queue and result summary tables.

While Bitbucket Data Center can deliver push events in rapid succession without guaranteed ordering, Bamboo's trigger handling processes each event independently. There is no documented exactly-once coalescing mechanism. Additionally, the Bamboo REST API utilizes offset-based pagination where query cost increases with offset, potentially contributing to latency spikes that only appear under parallel load.

• Does Bamboo Data Center provide any documented deduplication or coalescing logic for rapid successive webhook events targeting the same plan?
• What are the ordering guarantees for builds triggered by concurrent webhooks from Bitbucket?
• How does concurrent database contention affect REST API pagination response times for build and job data?