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
Community Members
Community Events
Community Groups

Bitbucket Webhook is not triggering Jenkins job even webhook returns 200

I am using bitbucket cloud and jenkins is running on ec2 instance on the private network. Connection is well established between bitbucket and jenkins as when i run the job manually, the job shows the green status. However when i made the changes in the repo and it gets merged but the webhook is not using my app password and as a result the job is getting failed.

I am getting authentication failed and It's basically asking me to use the app password. I have already created it but still webhook is not using it. I am getting the response 200 in webhook means my webhook is able to reach the jenkins server but i am not sure why i am getting authentication failed.

1 answer

0 votes
Mark C Atlassian Team May 29, 2022

Hi @sharat bhaskar

Welcome to the community.

I understand that you're using Bitbucket Cloud repository Webhooks to integrate to your Jenkins server running on an EC2 instance.
The Webhooks triggers fine but in your Jenkins server, you're getting an authentication error when you made the changes in the repository and it gets merged.

Based on the description and my understanding, the Jenkins server is still picking up your old credentials instead of the App password.
For this, would it be possible for you to try to clear your stored credentials related to Bitbucket Cloud in your EC2 instance and then try to re-authenticate again using your App password?

You can also refer to this community post for more information.

Hope it helps and do let me know how it goes.

Mark C

Suggest an answer

Log in or Sign up to answer
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...

2,231 views 2 9
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you