HSI Configuration & Deployment -- Enterprise Scheduler for Harmony Datasync (DEV/QA)

1 Introduction

Harmony Datasync application is requiring enterprise scheduler to trigger the event to push data, client info including parent and client, to Salesforce cloud.

2 Security Configuration

2.1 ACL setting

In Jenkins Admin Console, setup the Jenkins to use corporate AD server for user authentication

2.2 Create environmental credential

Create a credential with ID name: Scheduler-Credential, this credential is dedicated for authenticating and triggering the remote REST API to do the actual work

3  Jenkins Job Configuration

3.1 Create holder to organize the Jenkins jobs per project

3.2 Create a pipeline job in the new created folder

If there is other job existing, it is an easy way to copy from that job to create a new one. Simply typing the existing job name and go from there.

3.3 Give the job some basic information

The information includes :

• job name, the job name is mandatory to be unique. The recommended naming convention is pipeline-EVENTTYPE-PROJECT-APPNAME (ie: pipeline-nightly-harmony-datasync)
• designated running schedule in Regex: ie H(45-50) 23 * * 1-5. This value will be overwritten by the Jenkins Pipeline scripts
• Other setting will be overwritten by Jenkins Pipeline script

3.4 Load the Jenkins Pipeline script from Bitbucket Server

• Give the job a friendly name in Advanced Project Options for distinguishing purpose
• Use Pipeline script from SCM to load the pipeline script
• Select Git as SCM type
• Assign the actual repository URL
• Select the Jenkins/***** as the Bitbucket Credentials, this is a unified account for scheduler server to get the script from Bitbucket server
• Assign the value for branches to build
  1. for DEV environment, the branch is feature/xxxxx
  2. for QA environment, the branch is develop
  3. for Prod environment, the branch is master
• Set repository browser to Auto
• Set Script Path to Jenkinsfile
• Set Lightweight checkout to checked