Leveraging the OO Jenkins Plugin in DevOps scenarios

Transcription

1 Leveraging the OO Jenkins Plugin in DevOps scenarios HP OO Webinar, October 2015 Remus Golgot, HP Operations Orchestration RnD

2 Agenda Introduction Overview OO Jenkins Plugin Download and Installation Configurations Use Case : Automated OS Health Checks Solution Use Case : Automated Acceptance Testing Solution 2

3 Overview HP Operations Orchestration Leader in the IT Process Automation market Automates common tasks and processes in datacenters OO Community Content OO Jenkins Plugin Open source CI server Extensible through customizable plugins 3

4 OO Jenkins Plugin Download Install in Jenkins Global Configurations Local Configurations Get results 4

5 Download and Installation For latest released version : Jenkins-ci.org For latest version & contributions: github repository Install the plugin Stop the Jenkins service Copy the.hpi file in the JENKINS_HOME\plugins folder Start the Jenkins service 5

6 Configurations - Global Global dashboard: select Manage Jenkins -> Configure System scroll down to the HP Operations Orchestration field configure truststore and truststorepassword HP Operations Orchestration Server section: Unique Label -> Name of the OO server Host -> OO URL Username & Password -> Credentials Apply or Save -> Persist the changes 6

7 Configurations Job Level Select HP Operations Orchestration Server - Server label - Central to execute flow on Basepath - library path - contains the flow to execute Select Flow to Execute on Server - lists all the flow located in the basepath Add/Delete - adds/deletes flow inputs in the selected flow Refresh - update Select Flow to Execute on Server list Step Execution Timeout (ms) - number of ms the plugin will wait for each step 7

8 Demo Installation and Configuration

9 Use Cases Automated OS Health Checks Solution Automated Acceptance Testing Solution

10 Matrix Configuration Job Matrix: - Jenkins multi-configuration project - A collection of smaller jobs that perform similar tasks - If any of the smaller jobs fails, the main job will fail Each job runs a flow on a Central with a certain combination of inputs: Central Server Flow Inputs User defined axis Build step 10

11 Automated OS Health Checks Solution Axis configuration Build Step Filtering out combinations 11

12 Automated OS Health Checks Solution 12

13 Demo Automated OS Health Checks Solution

14 Automated Acceptance Testing Solution Jenkins job - runs a set of predefined tests - different versions of Central - different versions of the CP - triggered by an upstream project - triggers after a commit on that CP Automation Central machine - target of each flow invocation - each Central is installed on a slave 24 jobs that run all combinations <CP version, Central Version, Central OS > 14

15 Automated Acceptance Testing Solution Each cell downloads the OO installer, CP and corresponding Test CP Http Client silently installs the Central and deploys the CP and the Test CP Remote Command Execution runs the Test Flows inside the Test Content Pack Http Client Post ( against OO API ) or Dynamically Launch Flow ( HP Solutions CP ) creates status and coverage reports Custom operations that manipulate the JSON response returned by the API Each step corresponds to an OO Flow 15

16 Demo Automated Acceptance Testing Solution

17 Thank you