{"id":28829,"date":"2015-10-25T00:41:15","date_gmt":"2015-10-24T19:11:15","guid":{"rendered":"http:\/\/www.tothenew.com\/blog\/?p=28829"},"modified":"2016-01-19T13:29:21","modified_gmt":"2016-01-19T07:59:21","slug":"automated-docker-deployment-using-jenkins","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/automated-docker-deployment-using-jenkins\/","title":{"rendered":"Automated Docker Deployment using Jenkins"},"content":{"rendered":"

Building a Docker image from a Dockerfile, creating a latest tag and pushing it on DockerHub are equivalent to executing three different commands manually. This could be automated by creating a bash script.<\/p>\n

Well, that was not a big deal until I had a requirement where I needed to perform above actions and additional task of immediately triggering a “deployment job” already configured on Jenkins. The deployment job performs application deployment using recently updated Docker<\/a> image on desired servers running in my pre-production environment. So I needed something with which I could perform my task through Jenkins rather than running commands\/scripts on a shell. Since I am already using some Jenkins plugins in the current deployment job, so rather than creating a new deployment job I want to leverage the existing job.<\/p>\n

\"docker-jenkins\"<\/p>\n

In this quest, I came across a couple of Jenkins plugins provided by CloudBees which seemed perfect for this task. These plugins install\u00a0\u201cDocker Commons Plugin<\/strong>\u201d which provides a base functionality for Docker related plugins.<\/p>\n

CloudBees Docker Build and Publish plugin<\/strong>: It enables us to build images from the Dockerfile present on the server and publishing them on the DockerHub.
\nCloudBees DockerHub Notification<\/strong>: It enables us to trigger one or more Jenkins job by making use of DockerHub\u2019s web hook, thus creating a continuous delivery pipeline. Whenever a new image\u00a0is pushed, the configured Jenkins job will receive\u00a0notification as web hook and triggers the job.<\/p>\n

\n

Scenario:<\/strong> One click automation of a process of building image from Dockerfile, pushing it on DockerHub and immediately triggering a Jenkins deployment job based on the pushed docker image.<\/p>\n

\n

 <\/p>\n

\"Jenkins-CloudBees\"<\/p>\n

 <\/p>\n

    \n
      \n
    1. Installing Plugins:<\/strong>
      \nInstall the above two plugins using Jenkins\u2019 \u201cPlugin Manager<\/strong>\u201d.<\/li>\n
    2. Creating and configuring Jenkins job to build images from Dockerfile:<\/strong>
      \nCreate a new Jenkins job (say “Build Docker Image<\/em>“) which will use CloudBees Docker Build and Publish plugin<\/em> to build images from Dockerfile and push it on DockerHub.
      \nConfigure this job as follows under the build section:
      \n\"Jenkins1\"
      \nVarious fields in the above image are explained below:<\/p>\n
        \n
      • Repository Name<\/strong>: As shown we have passed \u201cnavjotsingh\/custom-image\u201d as the repository name.<\/span><\/strong><\/li>\n
      • Tag<\/b>: We are passing \u201cv1.0\u201d as tag or version. We can make this build parametrized and pass custom repository name and tag as two parameters to this job.<\/span><\/strong><\/li>\n
      • Docker Host URI<\/b>: Our Docker host is on the same machine where Jenkins is installed, so we are using default Docker \u2018s default URI by keeping this field empty.<\/span><\/strong><\/li>\n
      • Server credentials<\/b>: Provide user\u2019s credentials who has permission to run Docker commands and have permission to use Docker\u2019s socket \u201c\/var\/run\/docker.sock\u201d. I have provided permission to Jenkins\u2019 user.<\/span><\/strong><\/li>\n
      • Docker registry URL<\/b>: We are using public DockerHub registry so we have left \u201cDocker registry URL\u201d field empty.<\/span><\/strong><\/li>\n
      • Registry credentials<\/b>: Click \u201cAdd\u201d to add the DockerHub account credentials.<\/span><\/strong><\/li>\n
      • As we can see there are various options provided by this plugin wherein we can choose to <\/span>skip push, no cache, force pull and skip build<\/b>.<\/span><\/strong><\/li>\n
      • This plugin creates <\/span>fingerprints<\/b> after building image and are managed by Docker Commons Plugin (installed with this plugin).<\/span><\/strong><\/li>\n
      • Decorating the build name means builds will be decorated with the repository name and tag name. We can skip it by checking \u201c<\/span>Skip Decorate<\/b>\u201d check box.<\/span><\/strong>\"Jenkins6\"<\/li>\n
      • Skip tag as latest<\/strong>: If it is unchecked, it will create additional tag \u201clatest\u201d of the currently build image and push it on DockerHub as can be seen in the above image.<\/span><\/li>\n
      • Docker Directory is in<\/strong>: The directory which contain the Dockerfile can be specified in this field otherwise it will try to fetch the Dockerfile from the Job\u2019s workspace.<\/span><\/strong><\/strong><\/li>\n<\/ul>\n<\/li>\n<\/ol>\n<\/ol>\n

         <\/p>\n

          \n
        • Modifying existing Deployment Job to be triggered immediately after building image:<\/strong>
          \nNow we will modify the existing deployment job which we need to be executed whenever that Docker image is updated. We will achieve it by using CloudBees Docker Hub Notification plugin<\/strong>.
          \nConfigure the deployment job under \u201cBuild Triggers\u201d as follows:\"Jenkins7\"
          \nSelect \u201cMonitor Docker Hub image changes<\/strong>\u201d, under this select \u201cAny referenced Docker image can trigger this job<\/strong>\u201d. We can make this job to be triggered on specified repositories by selecting \u201cSpecified repositories will trigger this job<\/strong>\u201d and specifying repository name against \u201cRepositories<\/strong>” field. Multiple repositories can be specified in the text field, one repository per line.
          \n<\/span>Now, we have configured our deployment job to be triggered if any new image gets available in navjotsingh\/custom-image repository.<\/li>\n<\/ul>\n

           <\/p>\n

            \n
          1. Configuring webhook in DockerHub:<\/strong>
            \nNow, we need to configure webhook for our Jenkins server in the DockerHub as follows:<\/p>\n
              \n
            • Login to your DockerHub account.<\/li>\n
            • Select the repository which is \u201cnavjotsingh\/custom-image\u201d in our case.<\/li>\n
            • Click on \u201cWebhooks\u201d and then on “Add Webhook”.\"Jenkins3\"<\/li>\n
            • Provide your favourite Webhook name under \u201c Webhook Name\u201d field (say Jenkins Webhook).<\/li>\n
            • Provide below URL under \u201cHook URL 0\u201d.
              \nURL: http:\/\/\/dockerhub-webhook\/notify<\/li>\n
            • Click \u201cAdd URL\u201d as shown below:
              \n\"Jenkins8\"<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n

              That\u2019s all! We have completed the whole configuration to get our scenario working.<\/p>\n

              Summary<\/strong>: Upon our single click to start \u201cBuild Docker Image\u201d job, as a new image will be created from provided Dockerfile and pushed on to DockerHub. The new image pushed on DockerHub will trigger webhook notification to Jenkins server and this will trigger our \u201cDeployment Job\u201d to perform the deployment based on this new Docker image.<\/p>\n","protected":false},"excerpt":{"rendered":"

              Building a Docker image from a Dockerfile, creating a latest tag and pushing it on DockerHub are equivalent to executing three different commands manually. This could be automated by creating a bash script. Well, that was not a big deal until I had a requirement where I needed to perform above actions and additional task […]<\/p>\n","protected":false},"author":154,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":43},"categories":[1174,2348],"tags":[1853,2650,2414,1891,1883,2594,1682,2649],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/28829"}],"collection":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/users\/154"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/comments?post=28829"}],"version-history":[{"count":0,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/28829\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/media?parent=28829"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/categories?post=28829"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/tags?post=28829"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}