I have been experiencing problems with bitbucket and their post commit.
If you want to make BitBucket trigger a Jenkins job execution after a commit in your repo, you have two options:
Both using the Jenkins API to trigger the job.
For the POST hook, you basically need to build the url as this:
https://USER:APITOKEN@JENKINS_URL/job/JOBNAME/build?token=TOKEN
where:
The cool thing about this is that you can check if it works just using curl from the console.
Also note there is no password in the url, you have the API TOKEN instead, this is to avoid publishing your user and password. Something else you can do to improve security a little bit, if you have admin rights in the Jenkins server, create a new user with just access rights to read and build jobs, and use it only for this. So you don't have to publish your own user and token, which may have admin rights.
The Jenkins hook works the same way, building the same URL for you, but you don't have the chance to test it (for instance, using curl).
This is based on these documents:
Hope it helps.
Ger
This isn't really answering your question, but suggesting another approach. Both bitbucket.org and github.com support ssh keys.
See "Set up SSH for Git"
It is important to setup ssh-agent (explained in that page), as without this you'll be asked to enter a pass phrase instead of username and password.