anchor.diff:  
   Time permitting, to include behavior-driven development and automated deployment.
   
  -Lab objectives:
  +*Lab objectives:*
  +
   Examine the details of an end to end DevOps pipeline and participate in it using your development environment.
   
   You are now in 4 teams, each building a "feature" of the overall system managed throughout the pipeline.
   
  -In this lab, you will configure and instantiate your own VM that serves as a distributed development environment. You will change software that other students are also changing at the same time, and see how git is used to manage this.
  +In this lab, you will configure and instantiate your own VM that serves as a distributed development environment. You will change software that others on your team are also changing at the same time, and see how git is used to manage this.
   
   **In the following material substitute the 2-digit number you receive from the instructor, for XX**
   
  + [think about http://www.aha.io/]
  +
   == Clone the lab and vagrant up
   
   First, clone the "Lab O4" branch of Calavera thus (DON'T FORGET TO CHANGE XX TO YOUR 2 DIGIT #!):
   
  -    cd
  -    git clone https://github.com/StThomas-SEIS660/Calavera.git -b Lab-05 --single-branch manosXX
  + cd
  + git clone https://github.com/StThomas-SEIS660/Calavera.git -b Lab-05 --single-branch manosXX
   
   What does this do? Git repositories can be branched; a branch is a separate line of development. The Cala-dev branch gives you a single machine Vagrantfile to modify, making things a little easier for you.
   
  
positive.code: If you do not have either of these options, you can query the Jenkins API and at least see if a build has just run. Type
  
      java -jar /mnt/public/jenkins-cli.jar -s http://127.0.0.1:8133/ console hijoInit
  
negative.code: = Lab 04 (Technical) End to end DevOps product management
  
  == Overview
  
  