Bitbucket Server Docker image tag and Java version compatibility

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 with custom ACL plugins built for 7.x. The 'atlassian/bitbucket:latest' tag may point to a rolling release with experimental features not documented for production use. The git push webhook payload format differs between Bitbucket Cloud and Server 8.5, affecting third-party integrations that expect an older schema.

With these version-dependent changes, the compatibility of a pinned Docker image, its Java baseline, and downstream CI integrations is unclear.

Which official Docker image tag maps to a specific Bitbucket Server major version with a documented Java baseline? Does the 'atlassian/bitbucket:latest' tag include experimental features that change webhook payload schema or branch permission behavior? What version pinning approach preserves compatibility for CI pipelines that depend on stable webhook payloads and plugin APIs?