• tcw v2.04
• Introduction
  • Overview
  • Lab Flow Diagram
  • Architecture Diagram
  • Credentials Quick Reference
• Act I - Build
  • The App
  • Add some data to Production
  • Updating the Data Repository
  • Some Automation Details (part 1)
  • Viewing the Data Repository
  • Let’s Make Some Changes
  • We're Building!
  • Not So Fast!
  • Fix Our Script
  • We're Building! (Again)
  • Validate Our Build
• Act II - Test
  • Works in My Environment!
  • Automated Testing
  • Some Automation Details (part 2)
  • Oh Snap! A bug!
  • Ready to Test Again
  • Bugs Happen
  • Triaging the Bug
  • Squash the Bug
  • Deploy to Production

We’ve triggered an automated build of Patients Pipeline again. This time the Package Database Object Changes should complete successfully. The complete process can take around 4-8 minutes.

Here is the sequence of automation:

1. Jenkins is notified via a git post_update hook.
2. Jenkins executes the Patients Pipeline job against the develop branch, which does the following against our Patients Dev:
   • an Ansible role to compile the application
   • a Delphix job to refresh the development data pod
   • a Datical job to analyze and package the database object changes from our committed SQL scripts
   • a Datical job to forecast and deploy the packaged changes
   • an Ansible role to deploy the application

YOUR STEPS FOR THIS SCENE:

1. Bring Chrome to the foreground
2. Click on the Jenkins bookmark
3. Click on Patients Pipeline

   

   
   

4. You should see your build running. You can identify it by your commit message. Click that line.

   

   
   

5. OPTIONAL: Since our last build was halted before data was changed, we can skip the refresh this time:
   1. login to the Jenkins instance (credentials)

      

      
      

   2. When the build gets to the Refresh Data Pod stage, click Abort on the menu prompt.

      

      
      

6. The build will complete successfully, with all green checkmarks this time.