Bitbucket Webhook to Jenkins

[Quinn Wilson]

I experienced webhook network failures starting 3 days ago.

I gather that I now need to whitelist ip addresses in : 

https://bitbucket.org/blog/update-to-outgoing-webhook-ip-addresses

This doc (currently) contains 58 addresses - this seems like an unnecessary burden on a firewall admin.  

Three or four source IP addresses *was* reasonable. 

When will this be fixed?

edit: I can't even add that many source IP addresses to an AWS security group :
An error occurred (RulesPerSecurityGroupLimitExceeded) when calling the AuthorizeSecurityGroupIngress operation: The maximum number of rules per security group has been reached.

[Deleted user · Accepted solution]

Hey Quinn,

I found this:

https://bitbucket.org/blog/new-ip-addresses-bitbucket-cloud

Whitelisting these IPs solved our issue:

• IPv4: 18.205.93.0/25, 18.234.32.128/25, and 13.52.5.0/25
• IPv6: 2406:da00:ff00::0/96*

Hope it helps.

Best regards.

[Quinn Wilson]

Hey, seemed to work for me! Thanks Andrey!

[Frank Qi]

Looks like their documentation needs updating. It states that the IPs you mentioned are the CIDR blocks for incoming traffic to bitbucket.org, api.bitbucket.org, and altssh.bitbucket.org so I didn't want to add them unnecessarily.

Checked the Jenkins Multibranch Pipeline Log and I was getting traffic from

http://104.192.136.253 on Nov 29, 2018

... and after updating my firewall with your IPs I'm getting the webhook requests from

http://18.234.32.226 on Dec 5, 2018

Thanks for the info @[deleted]

[David Scavo]

Our webhooks also stopped working during this time period.

There has to be a better way that adding an additional 48 IP address ranges in AWS.

[Deleted user]

I'm experiencing the same issue that started at the same period.

Makes no sense for us to whitelist this quantity of IPs in our security group at AWS.

Is there any alternative to make this work without the need to whitelist all those IPs?