anchor.diff:  
   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:
  +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 with just one command line:
   
   ```
   $ ansible-galaxy -r requirements.xml
  
positive.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 start 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.
  
negative.code: $ ansible-galaxy install geerlingguy.jenkins
  ```
  
  You have to have internet connection so Ansible could connect on the repository and bring the role and all the dependencies it needs (maven, anyone?). After the installation process, check for the role installed on your system:
  
  ```
  $ ansible-galaxy list
  