DevOps Heroes

Adding automation integration

to your toolbox


A workshop based on Red Hat Process Automation Manager

Eric D. Schabell
Portfolio Architect Director
@ericschabell / http://schabell.org

Workshop goals

DevOps testing automation

This workshop is designed to introduce you to a new tool for your toolbox. The goal is to install a process automation environment, and build a process automation project integrating DevOps testing into a fictional organization. We'll introduce you along the way to the Red Hat Process Automation Manager and end up with a functional DevOps testing process.
Prerequisites (freely available): Java 8, Maven 3.6+, Red Hat Process Automation Manager 7.8, Red Hat Process Automation Manager Kie Server 7.8, JBoss EAP 7.3

DevOps basics

There are many aspects of DevOps sweeping organizations today, but it's important to review before we start the basic goals of DevOps. They focus on improvements to components in the delivery of your products and services, such as:
  • improved deployment frequency
  • faster time to market
  • lower new release failure rates
  • faster recovery from failures

DevOps practices

When discussing the best DevOps practices, there are hints as to why we're going to take a look at integrating process automation in your toolbox. Here are a few common practices you'll discover in the DevOps world:
  1. concentrate on PROCESS above tooling
  2. AUTOMATE build of application environemt
  3. AUTOMATE testing (security) of application
  4. AUTOMATE deploymen of applicaitont
This list shows why we're looking at a tool for capturing processes and enabling your DevOps automation.

New tooling

Red Hat Process Automation Manager

Take a closer look at the tooling you're adding to your toolbox:

The Project

DevOps testing (sub-)process

In this organization there's a large main process that automates the organizations DevOps. We'll be looking at a sub-process that automates the testing of a unit of code pushed by a developer:

What's in this process?

In this process a code job is submitted by a developer, the automated rules are applied to determine if a code review is needed by peers (+50 lines of code submitted). A review is possible and done by a senior group if needed. Diverse logging documents process flow as job moves through the process before heading back for deployment. Ideal jobs pass all rules and tests for automated deployment.

Workshop

Table of contents

  • Lab 1 - Install Red Hat Process Automation Manager
  • Lab 2 - Create a new project
  • Lab 3 - Create a data model
  • Lab 4 - Create a guided rule
  • Lab 5 - Create a process
  • Lab 6 - Completing process details
  • Lab 7 - Creating process and task forms
  • Lab 8 - Running the process
Let's get started at the beginning...