anchor.diff:  
   You should see the Jenkins role installed on your system provided with the version and all the other dependencies it needs. Ansible Galaxy works like many others package managers over there: it downloads all other required dependencies so you can work with it without any worries. Remember the Ansible Role's path set on step #2? Try to list the directory and you'll see all the roles there too.
   
  -Explore their work by looking for what the role really do. Start by exploring the `$ANSIBLE_ROLES_PATH/roles/geerlingguy.jenkins/tasks/main.yml`. Normally this is the starting point of the role and you really could see what's going on. Try to understand their code and how things are been doing there. It's a very nice exercise to learn by example and to absorb concepts harder to get on books or manuals.
  +Explore the role's creator work by looking for what the role really do. Start by exploring the `$ANSIBLE_ROLES_PATH/roles/geerlingguy.jenkins/tasks/main.yml`. Normally this is the starting point of the role and you really could see what's going on. Try to understand their code and how things are been doing there. It's a very nice exercise to learn by example and to absorb concepts harder to get on books or manuals.
   
   After that, be comfortable with their code and explore everything else, trying to understand how the pieces are working together to make the role that awesome.
   
  
positive.code: 
  This way we can tell Ansible that we need this role to perform our tasks.
  
  5 - `requirements.yml`. Besides the name, this isn't a required file for your project, but it's very handy because we can list all Ansible Galaxy's roles that we need and download then if just one line of command:
  
  ```
  $ ansible-galaxy -r requirements.xml
  
negative.code: 
  === The Bottom Line
  
  Now it's time to shine. Gather every role you could search for that you are going to use on your project and start chaining them together for awesomeness. In a short time you'll be creating your own roles, contributing for the ones already on the community and do a great job on your own playbooks. Just to help you out, take a look https://bitbucket.org/tecnobizz/vagrant-alm[at this project] that I did to provision all the three servers for a ALM process I was talking about at the begining of this post. There I orchestrate a simple playbook to create all the three machines using just three tasks: provision Jenkins, Sonar Source and Nexus.
  
  See you next time.
  