The "ara-report" role provides the same functionality and defaults
out of the box and adds integration for dynamic database loading.
This is removed as per the deprecation notice [1] a few months ago.
[1]: http://lists.zuul-ci.org/pipermail/zuul-announce/2018-March/000007.html
Change-Id: I1f5eda980b59cb43735d35a4670930f683dc0130
This changes the 'ara_generate_html' toggle to provide three options:
- true (always generate a report)
- false (never generate a report)
- 'failure' (only generate a report on failure, based on zuul_success)
This defaults to true and can be changed on a job basis.
Change-Id: I9a6a3c999b7656b1f5b25b0cb6c2baa63d7857b2
It might be useful for jobs to save the ARA sqlite database, for
example for debugging purposes, or if they want to import and use
the database elsewhere.
Change-Id: Ie82b42c34dfe6173116d88cc174deda70c5aa9ad
Without this patch, it is not possible for jobs to disable the
ara report generation because it is part of the base job by default.
It might be useful (or required) for jobs to disable the static
report generation if there are issues with it or if the static report
is causing problems. This toggle will provide that ability.
Change-Id: Ia5e43db9f852d405ea987b380e36cb93c983314d
The ARA web application was designed to work properly when fully
gzipped with the proper mimetypes so let's add support for doing
that.
Change-Id: Ic1914c840f5a75e7da07494fb87c2167ae7bed68