I have configured a Jenkins hook for a Bitbucket repo, and the configuration appears to be correct — when I reconstruct the URL it should be hitting using the values in the configuration, it fires off a Jenkins build.
I.e., When I hit `<endpoint>/job/<project name>/build?token=<token>` in my browser, it correctly triggers a build.
Here are the troubleshooting steps I have taken to try to resolve this issue:
X 0. Configured Jenkins commit hook.
Atlassian support checked it out, and it turns out that Jenkins is sending back a 403. I tried it out in another browser, and sure enough, even though I'm sending a token value, Jenkins is still showing the login page.
The next step will be to get Jenkins to allow a ping to the build URL (with appropriate token value) without requiring login.
When you need a quick pick-me-up, what do you turn to? It could be as simple as a piece of chocolate, a cup of tea, a funny YouTube video. Share your go-tos below!
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot