Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

jenkins hook not working - jenkins bitbucket

Hi i am using jenkins and bitbucket , i want to trigger a build in jenkins when ever i commit any thing to bitbucket repository .

in jenkins

  • i created a project called test_1
  • in configure section Build Triggers part i ticked Trigger builds remotely
  • i added a token TEST_TOKEN

when i type this in my browser url and execute the jenkins build is triggered

http://test.com:8080/job/test_1//build?token=TEST_TOKEN 

In bitbucket

i added a jenkins hook

  • Endpoint : http://test.com:8080/job/test_1//build?token=TEST_TOKEN
  • Module name - empty
  • Project name - test_1
  • Token - empty

then commited some code to bitbucket via git , The jenkins build not running , seems that the trigger is not running . :/ how to solve this problem . please help me . thanks in advance :)

like image 275
Kanishka Panamaldeniya Avatar asked Sep 15 '14 10:09

Kanishka Panamaldeniya


1 Answers

I had the same problem. @fmitchell is correct with his suggestions for these fields. But it didn't work for me.

I use a normal POST Hook instead where I provide the whole URL:

http://USER_NAME:[email protected]:YOUR_PORT/job/YOUR_PROJECT_NAME/build?token=some_token_from_jenkins

eg: http://[email protected]:8080/job/test_1/build?token=TEST_TOKEN

It seems to be that Bitbuckt is missing the last parameter "build" in its created URL, but I can't tell for sure.

------Update------

I found a better solution, where you don't only trigger your build but also be able do build different branches by different Jenkins projects:

  • Install Bitbucket Plugin at your Jenkins
  • Add a normal Post as Hook to your Bitbucket repository (Settings -> Hooks) and use following url:

https://YOUR.JENKINS.SERVER:PORT/bitbucket-hook

  • Configure your Jenkins project as follows:
    • under build trigger enable Build when a change is pushed to BitBucket
    • under Source Code Management select GIT; enter your credentials and define Branches to build (like **feature/*)

By this way I have three build projects, one for all features, one for develop and one for release branch.

And best of it, you don't have to ad new hooks for new Jenkins projects.

like image 128
salcosand Avatar answered Oct 18 '22 22:10

salcosand