You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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/
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:
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:
Please try to modify your whitelist and run the build again, let me know how this goes.
- Ben (Bitbucket Cloud Support)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.