I have bitbucket pipeline defined using the yaml file. One step is related to deployment - removing previous installation. Removing is done using the pipe "atlassian/ssh-run:0.4.2", the command is "rm...". However, after 2 minutes timeout (step execution is limited to 2 min), the step is declared as failed. Usually, time need for this command (step) to be executed is few seconds. The step is default size. Since no changes were inside the yaml file in the near past (the problem occurred this week, the last successful pipeline execution was 25 days ago ), I have doubt that the problem is in my internal network (firewall configuration) of it is related to the ip address range on the BB. This is my range used to set fw configuration:
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
188.2.97.71/32
13.236.8.128/32
18.246.31.128/32
185.166.140.0/22
18.184.99.128/32
52.215.192.128/25
104.192.136.0/21
18.205.93.0/27
18.136.214.0/25
13.52.5.0/25
18.234.32.128/25
Is this a sufficient set of addresses? All the addresses found in the atlassian-ip-ranges (https
/support.atlassian.com/bitbucket-cloud/docs/what-are-the-bitbucket-cloud-ip-addresses-i-should-use-to-configure-my-corporate-firewall/) are practically included here. Which specific address is used for SSH? For now, it's important to me to know that all the addresses are correct and none are missing, which would then lead me to believe the issue is in my internal network.
