Issue Summary

At this time, if a user clones another repository from the same workspace in pipelines with IP whitelisting enabled, they are required to whitelist the whole IP range that belongs to Bitbucket Pipelines. Considering the fact that both repositories in question belong to the same premium workspace, Can't the IP whitelisting feature be overridden in such cases? Or, could there be an option to just whitelist a set of repositories?

Steps to Reproduce

• Enable IP whitelisting on the workspace 'ABC'
• Go to repo 'A' and configure pipelines to clone the repo 'B'. Both repo 'A' and 'B' belongs to workspace 'ABC'
• The pipeline will error out with the following error: "To access this repository, an admin must whitelist your IP."

Expected Results

• Both repositories are part of the same workspace, therefore cloning another repo from the same workspace should be allowed and IP whitelisting check should be overridden.

Actual Results

• The user is required to add the Bitbucket pipelines IP range to the IP whitelisting section before cloning another repo within pipelines on the same workspace.

Workaround

• To add the Bitbucket pipelines IP range to the IP whitelisting section

  • 34.199.54.113/32
    34.232.25.90/32
    34.232.119.183/32
    34.236.25.177/32
    35.171.175.212/32
    52.54.90.98/32
    52.202.195.162/32
    52.203.14.55/32
    52.204.96.37/32
    34.218.156.209/32
    34.218.168.212/32
    52.41.219.63/32
    35.155.178.254/32
    35.160.177.10/32
    34.216.18.129/32