Today we lost the ability for our Bitbucket Pipelines executions to be able to reach our internal CICD and package repository endpoints.
We have followed https://support.atlassian.com/bitbucket-cloud/docs/what-are-the-bitbucket-cloud-ip-addresses-i-should-use-to-configure-my-corporate-firewall/ and whitelisted all IPs mentioned in this document, however we are still unable to hit our private endpoints from Bitbucket pipelines.
We have tested briefly having one open to the internet on HTTPS and it works as expected, so our belief is that Bitbucket pipelines is using an IP range not included in this document, nor any sensible ones in https://ip-ranges.atlassian.com/ where we filtered for IPs of the bitbucket product in regions eu-west-1, eu-west-2, or us-east-1.
Please can you support by suggesting IP ranges we should whitelist explicitly for running our Bitbucket pipelines, as the list in the supplied docs are seemingly incomplete.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.