Document a way to use ARA with Travis or other non persistent CI systems

[ssbarnea]

As probably anyone knowns, Travis does not have any embedded support to store build files, its only output is the build log. Users are expected to upload files to other systems during the build process, most of them do not do any such activity.

As use of Ansible on Travis got more popular it would be really useful to document a solution for making ARA reports available for builds made on such a limited CI. Having this on a sample git repository it would be great as people could look at how is implemented and replicate it to their own repos.

I am inclined to believe that the static approach is more likely to work because the database approach does not rule-out the need to a web-server, making the setup even more inconvenient. Maybe AWS S3 upload could be found ok?

[dmsimard]

@ssbarnea CI/CD is definitely a good use case for ARA and I agree that it probably deserves better documentation.

1.x is still somewhat in flux while we work on adding some missing features and so the end result might vary depending on how the features are implemented. I would probably wait until things have settled a little bit before writing new docs.

We are still working on the distributed sqlite backend, the static generation in ara-web and how ara-web might connect to arbitrary API endpoints.

In the meantime, I would definitely love to see how people might already be running ARA with Travis, Jenkins and other systems. We'd also need docs for Zuul.