{"id":133,"date":"2018-02-16T07:14:24","date_gmt":"2018-02-15T18:14:24","guid":{"rendered":"https:\/\/content.ronella.xyz\/apps\/wordpress\/?p=133"},"modified":"2018-02-16T07:14:24","modified_gmt":"2018-02-15T18:14:24","slug":"triggering-builds-remotely-with-jenkins-using-http-request-plugin","status":"publish","type":"post","link":"https:\/\/www.ronella.xyz\/?p=133","title":{"rendered":"Triggering builds remotely with Jenkins using HTTP Request plugin"},"content":{"rendered":"

Use Cases<\/b><\/p>\n

Lower Jenkins (e.g. v1.x)<\/i> but requires later Jenkins (e.g. v2.x) functionality (e.g. using git plugin which has some transitive dependencies which requires v2.x)<\/i>.<\/p>\n

For some reason , we just wanted a Jenkins server to delegate a task to another Jenkins server.<\/p>\n

You've created a script (i.e. python, ruby, groovy, etc)<\/i> that will trigger a Jenkins task via HTTP protocol. This is not part of this document but the Backend Jenkins Server<\/b> section is applicable.<\/p>\n

Backend Jenkins Server<\/b><\/p>\n

This is the server that will perform the task.<\/p>\n

Setting-up a role that can do remote build<\/b><\/p>\n

    \n
  1. Click Jenkins -> Manage Jenkins -> Manage and Assign Roles<\/b> entry and select Manage Roles<\/b>.<\/li>\n
  2. In the Global roles<\/b>, add a new role (e.g. remote_triggers)<\/i> that is allowed to trigger a task remotely.<\/li>\n
  3. Once added enable the following:<\/li>\n<\/ol>\n\n\n\n\n\n\n
    Overall<\/td>\nRead<\/td>\n<\/tr>\n
    Job<\/td>\nBuild<\/td>\n<\/tr>\n
    Job<\/td>\nRead<\/td>\n<\/tr>\n
    Job<\/td>\nWorkspace<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    Example 1: Sample role configuration<\/b><\/p>\n

    If we have remote_triggers<\/b> as the new role, we have the following:<\/p>\n

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

    Assigning a role to a user<\/b><\/p>\n

      \n
    1. Click Jenkins -> Manage Jenkins -> Manage and Assign Roles<\/b> entry and select Assign Role<\/b>.<\/li>\n
    2. In the Global roles<\/b>, add a known Jenkins user.<\/li>\n
    3. Once added assign the role.<\/li>\n<\/ol>\n

      Example 2: Assign a role following Example 1.<\/b><\/p>\n

      If the known user is GwDevOpsDev<\/b>, we have the following:<\/p>\n

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

      Setting-up the Build Triggers<\/b><\/p>\n

        \n
      1. On the Build Triggers<\/b> section, select the Trigger builds remotely (e.g., from scripts)<\/b>.<\/li>\n
      2. Provide an Authentication Token<\/b>.<\/li>\n<\/ol>\n

        Note: You can use <\/i>https:\/\/www.guidgenerator.com\/<\/i><\/a> just remove the hyphen for this.<\/i><\/p>\n

        This will enable you to trigger the job remotely via HTTP Post using one of the following:<\/p>\n

        Without Build Parameters<\/b><\/p>\n

        <JENKINS_URL>\/job\/<URL_ENCODED_ITEM_NAME>\/build?token=<AUTHENTICATION_TOKEN><\/pre>\n
        With Build Parameters<\/b><\/p>\n
        <JENKINS_URL>\/job\/<URL_ENCODED_ITEM_NAME>\/buildWithParameters?token=<AUTHENTICATION_TOKEN><\/pre>\n
        Example 3: Address to call a task remotely.<\/b><\/p>\n
        If we have the following:<\/p>\n
        JENKINS_URL = http:\/\/d-51306g2.fmg.net:9080<\/a>\r\nITEM_NAME=Statement Date Update to Saturday\r\nURL_ENCODED_ITEM_NAME=Statement%20Date%20Update%20to%20Saturday\r\nAUTHENTICATION_TOKEN=49dcf6a2164147b1871de70b40afef6f<\/pre>\n
        The URL to call this job remotely with build parameters must be:<\/p>\n
        http:\/\/d-51306g2.fmg.net:9080\/job\/Statement%20Date%20Update%20to%20Saturday\/buildWithParameters?token=49dcf6a2164147b1871de70b40afef6f<\/pre>\n
        User Facing Jenkins Server<\/b><\/p>\n
        This is the Jenkins server that is normally use by the user to invoke tasks but the task is actually being done by a another Jenkins server.<\/p>\n
        Pre-requisite<\/b><\/p>\n