{"id":8366,"date":"2018-02-08T03:01:54","date_gmt":"2018-02-08T08:01:54","guid":{"rendered":"https:\/\/qxf2.com\/blog\/?p=8366"},"modified":"2018-03-29T10:38:27","modified_gmt":"2018-03-29T14:38:27","slug":"blog-post-on-how-to-connect-bitbucket-with-jenkins","status":"publish","type":"post","link":"https:\/\/qxf2.com\/blog\/blog-post-on-how-to-connect-bitbucket-with-jenkins\/","title":{"rendered":"Bitbucket integration with Jenkins"},"content":{"rendered":"

In this post, we will learn to setup Continuous Integration using Jenkins and Bitbucket. As soon as a commit happens on Bitbucket, it should trigger a Jenkins Job. To do this, we are going to create webhook on Bitbucket and supply it to a Jenkins job. This webhook will notify Jenkins about all new commits, information about the branch, commits that are made, etc.<\/p>\n

\n

Why this post?<\/h3>\n

We did not find a short explanation about configuring Bitbucket with Jenkins. So wanted to consolidate that information in one post.<\/p>\n

\n

Overview of integrating Bitbucket and Jenkins<\/h3>\n

1. Install a Jenkins plugin for Bitbucket
\n2. Configure your Jenkins job with Bitbucket repository details
\n3. Verify your Jenkins configuration looks ok
\n4. Configure a Webhook on Bitbucket
\n5. Exercise your integration
\n6. Check the Bitbucket Hook log<\/p>\n

\n

Detailed guide to integrate Jenkins and Bitbucket<\/h3>\n

1.Install and configure a Jenkins plugin for Bitbucket <\/strong>
\nThis can be done under Manage Jenkins<\/strong> — Manage Plugins<\/strong> — Search for Bitbucket Plugin<\/strong> and install the same.To know more about the Bitbucket plugin,can have a\u00a0look at https:\/\/wiki.jenkins.io\/display\/JENKINS\/BitBucket+Plugin<\/a>.<\/p>\n

2. Configure your Jenkins job with Bitbucket repository details<\/strong>
\nConfigure Bitbucket Repository under Source Code Management, along with credentials.<\/p>\n

\"source_code_management\"<\/a><\/p>\n

3. Verify your Jenkins configuration looks ok<\/strong>
\nTo check whether Bitbucket Plugin got installed on Jenkins, go to Job<\/strong>—Build Triggers<\/strong> and you should be able to see option as “Build when a change is pushed to BitBucket<\/strong>”<\/p>\n

\"bitbucket_plugin\"<\/a><\/p>\n

4.\u00a0Configure a Webhook on Bitbucket<\/strong>
\nOn Bitbucket, go to Settings<\/strong> — Webhook<\/strong> — Add Webhook<\/strong>.<\/p>\n

\"configuring<\/a><\/p>\n

Add a Webhook, as above given in the picture.The format of the URL is \u00a0http:\/\/<jenkins IP-address><\/strong>\/bitbucket-hook<\/span>\u00a0. The webhook should be active. So, click the option “active”. Under “Triggers<\/strong>” add “Repository Push<\/strong>” option and save the Webhook.<\/p>\n

NOTE:<\/strong> Trailing slash should be there at the end of\u00a0 URL.<\/p>\n

5. Exercise your integration<\/strong>
\nMake a change to your code base and push it to Bitbucket. Check on Jenkins whether build gets triggered.<\/p>\n

\"git\"<\/a><\/p>\n

6. Check the Bitbucket Hook log<\/strong>
\nOn Jenkins, when the build is triggered by Bitbucket webhook, you can check the activity under BitBucket Hook Log<\/strong>.<\/p>\n

\"bitbucket_hook_log\"<\/a><\/p>\n

In this way, we can do Bitbucket Integration with Jenkins. If you liked this article, learn more about Qxf2’s<\/a> testing services for startups.<\/strong><\/p>\n

\n

References<\/h3>\n

1. A useful 8-minute video <\/a><\/p>\n

2. A more developer-friendly version of this post<\/a><\/p>\n

\n","protected":false},"excerpt":{"rendered":"

In this post, we will learn to setup Continuous Integration using Jenkins and Bitbucket. As soon as a commit happens on Bitbucket, it should trigger a Jenkins Job. To do this, we are going to create webhook on Bitbucket and supply it to a Jenkins job. This webhook will notify Jenkins about all new commits, information about the branch, commits […]<\/p>\n","protected":false},"author":21,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[143,52,51],"tags":[],"class_list":["post-8366","post","type-post","status-publish","format-standard","hentry","category-bitbucket","category-continuous-integration","category-jenkins"],"_links":{"self":[{"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/posts\/8366","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/users\/21"}],"replies":[{"embeddable":true,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/comments?post=8366"}],"version-history":[{"count":28,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/posts\/8366\/revisions"}],"predecessor-version":[{"id":10966,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/posts\/8366\/revisions\/10966"}],"wp:attachment":[{"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/media?parent=8366"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/categories?post=8366"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/tags?post=8366"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}