• tcw v2.14
• 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
• Archives
  • v2.04
  • v2.13

If you develop applications for a living, you will be the author of many bugs over the course of your career. One of the challenges of fixing bugs is the ability to reproduce the issue. The easiest way to do this is to see the bug in its failed state. But, when bugs are found upstream, that usually means tying up environments until the developer can “come to your desk” and take a look at the environment to triage the issue.

The Delphix DDP allows you save and share data state between data pods. This allows us to treat data as code: cloning and branching as needed. When you can get the exact state of data you need , on demand, your environments and operations are no longer held hostage by data.

In the last scene, we saved the data state of the failed test in our Test data pod. Though we realize this situation would be simple to recreate manually, in this scene we are going to “pause” the current data in our Develop data pod, and replace it with the data from the bug bookmark that was automatically created in the last scene.

YOUR STEPS FOR THIS SCENE:

1. Bring the Delphix Engine tab to the foreground
2. If you are still logged in as qa, then logout

   

   
   

3. Login as the dev user. The password is delphix

   

   
   

4. If this is your first login, you will be prompted to change the password. Set the password to delphix

   

   
   

5. You should now be in the Data Operations screen. Click on Develop data pod

   

   
   

6. You should now see the timeline for Develop data pod. Click on the Bookmarks button.

   

   
   

7. By default, you’ll only see the bookmark that was automatically generated when our initial build failed (column name). Click Available.
8. You should now see bookmarks that have been shared with you from other data pods.

   

   
   

9. Bookmarks are searchable. Search for the bookmark that corresponds to your bug or test from Act I. In the example below, my bug is Bug 3.

   

   
   

10. Click the boomark.
11. Click the branch icon (purple box, below)
12. Name the branch after your bug, ex. bug 3
13. Click Create.

    

    
    

14. Click Timeline.
15. You will now see the Creating Branch progress bar. After completion, proceed to the next step.

    

    
    

16. When it is complete, you will see the name of your new branch across the top and you will see that the timeline of the data pod starts from the bookmark you had previously selected.

    

    
    

17. Go back to the bookmark and copy the git hash from the tag to your clipboard

    

    
    

18. Open a terminal window and enter deploy_dev <git commit hash>.