Trigger a jenkins build from git using cloudbees and bitbucket

I’m trying to trigger a jenkins build automatically when i commit to my git repo. I am using a cloudbees jenkins instance and my repo is located at butbucket.

I configured the jenkins service on my bitbucket repo but it doesn’t seem to start the build on jenkins. To configure it i’ve used the following:

  • Bitbucket/Github: permission denied public key
  • When I “git push” git now says “Create pull request for …”. Why?
  • How do I import specific or old commit from bitbucket using eGit in eclipse
  • Bitbucket git credentials if signed up with Google
  • bitbucket stripped git revisions
  • Why is Jenkins getting Authentication Failed error for git submodule update?
  • Endpoint: https://<my-email>:<my-api-token>@myaccount.ci.cloudbees.com
    Project name: <my-build-job-name>
    Token: <my-token-name>
    

    I have properly set up both the cloudbees SSH public key to bitbucket and verified that jenkins does build my project successfully when triggered manually. It doesn’t seem to work however when i push changes to my repository.

    I have followed the following tutorial: http://wiki.cloudbees.com/bin/view/DEV/Bitbucket

    Has anyone managed to solve this?

  • SourceTree Staging Error
  • Show both tags and branches in Bitbucket under commits view
  • Test to determine if git clone command succeeded
  • Git - How do I revert my local files to the last commit i made?
  • How to pass a build number within the MultiJob plugin?
  • Understanding Git with XCode and BitBucket
  • 3 Solutions collect form web for “Trigger a jenkins build from git using cloudbees and bitbucket”

    I also followed the CloudBees BitBucket Tutorial
    but what I found is that I had skipped a step as it had been in french.

    The step was to check (in the Jenkins Configuration) the Trigger builds remotely (e.g., from scripts) checkbox and ensure that the Authentication Token given is the same Token that is given to the BitBucket Service. This, as the tutorial says, is where “the magic will occur”.

    I wrote this doc about intergating bitbucket with jenkins on Cloudbees, but bitbucket don’t officially support credentials on service hooks, and this doesn’t seem to work for ALL accounts, even I can’t tell why it sometimes fails. Cloudbees instance just never receive the notification http request with credentials set.

    Maybe a bitbucket plugin would help, as we have for github and gitlab to manage commit hooks.

    I posted a related solution here for others who happen to land on this page.

    Git Baby is a git and github fan, let's start git clone.