{"id":4276,"date":"2015-03-23T00:29:20","date_gmt":"2015-03-23T00:29:20","guid":{"rendered":"http:\/\/www.jitendrazaa.com\/blog\/?p=4276"},"modified":"2015-03-23T04:03:00","modified_gmt":"2015-03-23T04:03:00","slug":"continuous-integration-in-salesforce-using-jenkins-and-git-video-tutorial","status":"publish","type":"post","link":"https:\/\/www.jitendrazaa.com\/blog\/salesforce\/continuous-integration-in-salesforce-using-jenkins-and-git-video-tutorial\/","title":{"rendered":"Continuous integration in Salesforce Using Jenkins and Git | Video Tutorial"},"content":{"rendered":"

As your Salesforce Organization undergoes heavy customization and frequent builds, moving changes from one Sandbox to other sandboxes starts taking longer time and effort. Also, in normal Salesforce project, there are chances that you will have minimum three sandboxes likely Developer Sandbox, QA Sandbox and UAT Sandbox. After some time you will be in need of some solution which can reduce your effort.<\/p>\n

Almost 5 years back, when I was working on .net along with Salesforce, I posted article on Continuous Integration of ASP.net and subversion as a code management with MSBuild on code project<\/a>.<\/p>\n

This time its Salesforce using Jenkins.\u00a0In this article I will walk through solution of above\u00a0problem using Jenkins<\/a>. Don’t forget to watch Video at end of this article, where I provided demo of everything explained in this article.<\/p>\n

Prerequisite Software:<\/p>\n

    \n
  1. ANT<\/a><\/li>\n
  2. Salesforce Migration Tool<\/a><\/li>\n
  3. Git<\/a><\/li>\n
  4. Eclipse <\/a>or PuTTYgen\u00a0<\/a>to generate SSH key<\/li>\n<\/ol>\n

    I am assuming\u00a0you already know about below concepts:<\/p>\n

      \n
    1. How to use Git with Salesforce<\/a><\/li>\n
    2. Using ANT migration tool in Salesforce<\/a><\/li>\n
    3. Generating SSH key<\/a><\/li>\n
    4. Automated Daily Backup of Salesforce Using ANT Migration Tool and GIT<\/a>\u00a0(Optional)<\/em><\/li>\n<\/ol>\n

      I will suggest to get familiar with first three\u00a0topics before jumping to Continuous Integration.<\/p>\n

      There are two ways to start working with Jenkins<\/p>\n

        \n
      1. Install Jenkins on your local system<\/li>\n
      2. Use Cloudbees <\/a>online<\/li>\n<\/ol>\n

        Below diagram shows complete flow of Continuous Integration we are going to setup in this article.<\/p>\n

        \"Continuous<\/a>
        Continuous integration in Salesforce Using Jenkins and Git (Bit Bucket)<\/figcaption><\/figure>\n

        For this tutorial, I will install Jenkins on my local system. To install it, Navigate to Jenkins homepage and download installer<\/a>.<\/p>\n

        During installation, you may be prompted to install Jenkins as “Windows Service”, click yes for that option. Once installed navigate to “http:\/\/localhost:8080”, and you should be able to Jenkins homepage.<\/p>\n

        Installing Git plugin<\/strong><\/p>\n

        By default Jenkins does not provide support for Git, so we will need to install it separately.<\/p>\n

        To install Git Plugin, Navigate to “Jenkins Homepage | Manage Jenkins | Manage Plugins | Available” and search for Git. From available list, install “Git Plugin”. I would suggest to install “Bitbucket Plugin” as well.<\/p>\n

        Installing chatter Plugin<\/strong><\/p>\n

        Once Git plugin is installed, we will need to install chatter plugin as well from superfell’s\u00a0github repository<\/a>. Assuming you already have Maven installed on your system, download above repository as a zip and extract it on your system. After extract, run command “mvn” in that directory. It will create folder by name “target” and plugin file by name “ChatterPlugin.hpi” would be available.<\/p>\n

        If you don’t want to perform maven build then you can bypass above step and download file from here<\/a>, however it is always suggested to build file from latest repository code. If you are downloading “ChatterPlugin.hpi” from my website then don’t forget to rename file to “ChatterPlugin.hpi”.<\/p>\n

        Once you have “ChatterPlugin.hpi” file on your system, you need to install it into Jenkins. Navigate to “Jenkins Homepage | Manage Jenkins | Manage Plugins | Advanced | Upload Plugin”. Select “ChatterPlugin.hpi” and upload it.<\/p>\n

        Salesforce migration ANT script<\/strong><\/p>\n

        Now, we need to create “build.xml” to retrieve changes from one Org and Deploy to other Org. Assuming, you already know how to use ANT Migration tool<\/a> I will directly show code snippet of my “build.xml” file.<\/p>\n

        \r\n<project name="Code Backup Without Folders" default="retrieve" basedir="." xmlns:sf="antlib:com.salesforce">\r\n\t<property file="build.properties"\/>\r\n\t<property environment="env"\/>\r\n  <target name="Deploy">\r\n\t<sf:deploy\r\n\t\t\tusername="${Sandbox2.username}"\r\n\t\t\tpassword="${Sandbox2.password}"\r\n\t\t\tserverurl="${sfSandbox.serverurl}"\r\n\t\t\tdeployRoot="${Sandbox2.retrieveTarget}"\r\n\t\t\trunAllTests="true" \/>\r\n  <\/target>\r\n  <target name="retrieve">\r\n\t  <sf:retrieve username="${Sandbox1.username}"\r\n\t\t\t\t   password="${Sandbox1.password}"\r\n\t\t\t\t   serverurl="${sfSandbox.serverurl}"\r\n\t\t\t\t   retrieveTarget="${Sandbox1.retrieveTarget}"\r\n\t\t\t\t   unpackaged="${Sandbox1.unpackaged}"\/>\r\n        <echo message="Commiting all changes with message ${gt.commitMessage}" \/>\r\n\t\t<git command="add" dir="${Sandbox1.gitDirectory}">\r\n\t\t\t<args>\r\n\t\t\t\t<arg value="." \/>\r\n\t\t\t<\/args>\r\n\t\t<\/git>\r\n\t\t<git command="commit" dir="${Sandbox1.gitDirectory}">\r\n\t\t\t<args>\r\n\t\t\t\t<arg value="-am ${gt.commitMessage}" \/>\r\n\t\t\t<\/args>\r\n\t\t<\/git>\r\n\t<\/target>\r\n\t<macrodef name="git">\r\n\t\t<attribute name="command" \/>\r\n\t\t<attribute name="dir" \/>\r\n\t\t<element name="args" optional="true" \/>\r\n\t\t<sequential>\r\n            <echo message="Executing Command in folder @{dir}" \/>\r\n            <echo message="git @{command}" \/>\r\n\t\t\t<exec executable="git" dir="@{dir}">\r\n\t\t\t\t<arg value="@{command}" \/>\r\n\t\t\t\t<args\/>\r\n\t\t\t<\/exec>\r\n\t\t<\/sequential>\r\n\t<\/macrodef>\r\n<\/project>\r\n<\/pre>\n
        Username, Passwords and other values are coming from “build.properties” file. As you can see in above code, Changes are fetched from “Sandbox1” and deployed to “Sandbox2”.<\/p>\n
        Setting-up Bitbucket account<\/strong><\/p>\n
        If you are following my blog, you may already know that I give preference to Bitbucket over Github because it allows me to setup private repository free of\u00a0cost.<\/p>\n
        First you will need to generate SSH key for authentication, for this you can either use Eclipse or PuTTYGen. In Video demo of this article, i have used PuTTYGen. Once SSH key is generated, upload Public key in Bitbucket by navigating to “Manage Account | Securtiy | SSH Keys | Add Key”. Save Private key with extension “ppk” somewhere on your local system.<\/p>\n
        You will need to commit all your changes of “Sandbox1” to this Bitbucket account so that it can be deployed to “Sandbox2”. For this you can either use Eclipse <\/a>or TortoiseGit.<\/p>\n
        Create new project in Jenkins<\/strong><\/p>\n
        Navigate to “Home page | New Item”. Give appropriate item name and then choose “Freestyle project”.<\/p>\n
        \"Create<\/a>
        Create New Item in Jenkins – Free Style Project<\/figcaption><\/figure>\n
        In “Source Code Management”, choose “Git”. In Repository URL, provide repository URL of Bitbucket for SSH protocol. In Credentials, click on Add, choose “SSH Username with private key”. Provide username and paste private key saved in “ppk” file. If there is any Passphrase then provide it and save it.<\/p>\n
        \"Jenkins<\/a>
        Jenkins SSH Username with private key Credentials<\/figcaption><\/figure>\n
        Build Triggers<\/strong><\/p>\n
        There may be any combination which will cause Jenkins to trigger build. For example if code is pushed to your Git repository, or poll Git repository after some predefined interval to see if there is any change or run build periodically. You can have one or more than one combination to trigger builds. In this article I have selected “Poll SCM” option. It will check my git repository after every 15 minutes for changes \u00a0and if it finds that repository has been changed then it will start building. If you select “Pol SCM”, then text box will appear where we need to provide crone statement to decide its scheduled time. I have provided “H\/15 * * * *”<\/span> which means, it will run every 15 minutes.<\/p>\n
        Build\u00a0<\/strong><\/p>\n
        In this section choose “Invoke Ant”. \u00a0In Targets, provide Ant target names separated by space. provide location of folder where “build.xml” is present in text box “Build File”.<\/p>\n
        \"Jenkins<\/a>
        Jenkins build – Invoke Ant task<\/figcaption><\/figure>\n
        Post-build Actions<\/strong><\/p>\n
        In this section of project configuration, we need to setup task that can be executed after build. There are number of options available, however we will choose “Chatter results”. This task will be available only if you have installed “Chatter plugin” as explained above. Here, we need to provide Username and Password to connect to Salesforce. If you want to connect to Sandbox or My Domain then need to setup value in text box “Override Login Server” else keep it blank.<\/p>\n
        \"Jenkins<\/a>
        Jenkins Post build Action – Post to Salesforce Chatter<\/figcaption><\/figure>\n
        After all above settings, save this information and we will be good to go. You can see log of attempt by Jenkins to determine if there is any change in git repository, it would be available at left menu by name “Git Polling Log”.<\/p>\n
        \"Salesforce<\/a>
        Salesforce – Jenkins Git Polling Log<\/figcaption><\/figure>\n
        We can also manually trigger build by clicking on “Build Now” link visible in above image. All build results will be available below “Git Polling Log”.<\/p>\n
        Video Tutorial<\/strong><\/p>\n