Overview

Perform operations on Builds, and Jobs via the Workflow Automator. This app communicates with the on-premise Jenkins using the orchestration server.


Description

Orchestration apps let you automate repeatable tasks and actions that span across a diverse set of systems and applications using workflows. The list of actions supported for this app include:

1. Build Management

  • Get Build ID

  • Get Build Timestamp

  • Get Console Output

  • Get Build Information

  • Get Build Number

  • Build

  • Delete Build

2. Job Management

  • Copy Job

  • Create Folder

  • Create Job

  • Delete Folder

  • Delete Job

  • Get Job Configuration

  • Reload Job

  • Rename Job


Working Principle

The app communicates with the on-premise Jenkins with the help of the Orchestration server, which resides in the same private network as Jenkins and acts as an agent.



Prerequisites

  1. Orchestration Server Installation

Orchestration server should be installed using the installer, on a windows server. 

This installer can be found in your Freshservice tenant in the Admin > Helpdesk Productivity > Orchestration Centre > Orchestration Server > “Download Windows Installer”.

To know more about the orchestration server installation please refer to the

Orchestration Server solution article.


Verify Connection Using “Test App Action”

You can also use the “Test App Action” functionality inside the Workflow Automator’s App Node to verify the connection between the Orchestration server and On-Premise Jenkins.



Note: Please ensure that Jenkins should be accessible from the Orchestration server. You can use a telnet utility to verify the connectivity.



Installation Parameters

To install and authenticate this app you will need to provide the following inputs

  • Jenkins URL

  • Username

  • Password or API Token


Steps to acquire apps credentials

  1. Jenkins URL can be found in the web browser’s address bar


  1. The username and password are the same as what is used while logging in to Jenkins. Earlier versions of Jenkins require you to specify your real password.  Specifying the real password is still supported, but it is not recommended because of the risk of revealing the password, and the human tendency to reuse the same password in different places.

  2. The API token is available on your personal configuration page. Click on your name on the top right corner on every page, then click "Configure" to see your API token.