I have added bitbucket webhook for jenkins integration in my repository settings but it is returning 403 error. The webhook URL is provided in the following format:
The username provided also have admin access in Jenkins still it is giving :
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>403 Forbidden</title> </head><body> <h1>Forbidden</h1> <p>You don't have permission to access /bitbucket-hook/ on this server.<br /> </p> </body></html>
I have tried all the combinations like username:password instead of API token but it is throwing error in all conditions.
Just to let you know that Jenkins can successfully pull the code from bitbucket when the job is triggered manually.
The 403 status is actually pretty descriptive here: it means that user doesn't have permission to that endpoint (/bitbucket-hook). The network is fine (otherwise you would get a NET_ERR), and the credentials themselves are OK (otherwise you would get a 401), and there's an endpoint by that name (otherwise you would get a 404), but the user in question is just not allowed to do that action.
You should examine the listener's configuration on Jenkins - that's where the issue appears to be. Look especially for user permissions.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs