anchor.diff:  
   Discuss with your team what this does and how it works. In particular, review what the hombrosxx server does.
   
  +=== A first look at Jenkins
  +
   So, when hombrosxx receives the call from the githook, how does it know what to do? Go to your X-windows Firefox, and open the hombros tab with the Jenkins GUI.
   
   image::hijoInitLink.png[]
  
positive.code: 
  The last command is likely unfamiliar. What is it?
  
  Look again at the Calavera architecture:
  
  image::http://dm-academy.github.io/aitm/images/1.03-pipeline.png[]
  
negative.code: 
  By this point, Jenkins' centrality should be clear. However, on this first pass through the architecture, there is one more step, that of deployment.
  
  At this time, we are not doing full Continuous Deployment in the lab, as it's not clear that this is always a best or desirable practice. You develop on manos, check into cerebro, and if all tests pass you have a newly built package in espina ready for deployment, but the actual deployment still requires one more positive step. Going back to your ssh session:
  
  ....
   vagrant@manos1:~$ exit
  logout
  Connection to 127.0.0.1 closed.
  public1@seis660:~/Calavera$ vagrant reload --provision cara1
  ==> cara1: Loading Berkshelf datafile...
  ....
  
  Usually, vagrant is not used to run production systems, but by typing `vagrant reload --provision` you force chef to check if the deployed packages are up to date. Since you have had (presumably) a successful Jenkins build since the last provisioning, the deployed .jar files on caraxx are *not* up to date, and will be replaced by the most recent files in Artifactory. Go to firefox and check, once the reprovisioning process is complete. The change you made and committed above should now be visible in caraxx, our "production" system.
  
  == Further exercises
  
  ****
  *Instructor's note*
  
  We are going to enter into a more creative phase of the class. This class is itself a product and I am looking for feedback on the lab experience and platform. You now have a workable set of tools similar to an industrial environment, and I want to let you determine to some degree what you are interested in.
  ****
  
  Here are some ideas for the remainder of the evening (please stay for the full class). Think about what you'd like to learn over the next 2-3 labs.
  
  === Product suggestions
  Start developing a product identity. As a team, develop some simple product ideas. These can be very basic things like:
  
  * Display a mascot or brand for your team
  * Take a person's name and say "Hello" back to them
  * Perform simple math calculations
  
  Take a LIMITED amount of time and come up with 3-5 such features that your developers think they can implement.
  
  === Development suggestions
  * Break your build
  * Revert back to a known good version
  * Experiment with Javascript for implementing simple logic on the page
  * Features must have tests.
  * What would it take to set up a database and integrate it with your Java?
  
  IMPORTANT: Any source code you check into local git on manosxx or central git on cerebroxx is not backed up, unless you take steps to do so.
  
  === Toolchain suggestions
  * Look at all aspects of the pipeline. Don't be afraid to experiment. It's yours and if you break it we will just rebuild it.
  * Learn to rebuild part or all of your development pipeline
  * Trace a configuration setting in the pipeline back to the Chef recipe that specified it.
  * Figure out how to replicate any code you write in the pipeline to Github (it is not backed up otherwise).
  * Help the developers set up a database.
  