Sometimes travis introduces changes into their infrastructure causing our .travis.yml jobs to stop working.

Say a database upgrade, some OS bump... it happens from time to time.

This is about to create a job into our CI infrastructure continuously checking that everything is ok with travis.

Sending (force) some branch, or maybe triggering via API... the idea is to ensure that it's passing. Nothing more, nothing else.