Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,361,334
Community Members
 
Community Events
168
Community Groups

want to trigger a jenkins job via bitbucket pipeline but getting 403 error

mine Jenkins server is running on AWS and not available from everywhere only available to access from Office IP. I generated a token from going to the user setting in Jenkins and used that token in Bitbucket Pipeline to trigger the Jenkins pipeline. But I am getting a 403 error. I try to allow 443 or 80 ports from anywhere but still no luck. I know I am missing something but... i used pipe https://bitbucket.org/atlassian/jenkins-job-trigger/src/master/

1 answer

1 vote
Ben Atlassian Team Aug 10, 2022

Hi Muhammad,

Welcome to the Bitbucket Cloud Community! :) 

The error which you have mentioned 403 can occur for a number of reasons, however - given that you are running your server on AWS, the most likely cause is due to IP whitelisting.

Please refer to the following documentation below and ensure the relevant IP's are whitelisted on AWS to allow Pipelines to interface with the service:
https://support.atlassian.com/bitbucket-cloud/docs/what-are-the-bitbucket-cloud-ip-addresses-i-should-use-to-configure-my-corporate-firewall/

To test the actual IP address that your build is using, you can add the following command to your build step - this should match one of the IP ranges specified above:

curl http://checkip.amazonaws.com/

Please try to modify your whitelist and run the build again, let me know how this goes.

Cheers!

- Ben (Bitbucket Cloud Support)

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Bitbucket

Git push size limits are coming to Bitbucket Cloud starting April 4th, 2022

Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...

3,494 views 3 10
Read article

Atlassian Community Events