(removing leftover trac syntax, added category) |
(re-do layout, add missing conf files) |
||
| Line 1: | Line 1: | ||
Most of the configurable settings in AutoQA are well documented in the comments of the configuration files. Here is the list of AutoQA's configuration files and some further information that wouldn't fit in the config files themselves. | |||
= General configuration = | |||
= Bodhi Comment Email Settings = | [https://fedorahosted.org/autoqa/browser/conf/autoqa.conf {{filename|/etc/autoqa/autoqa.conf}}] | ||
Some of the settings used to configure the behavior of emails sent when Bodhi comments are sent by AutoQA require a bit more explanation than what is contained in | |||
This is the main configuration file where all the general settings are available. | |||
== Bodhi Comment Email Settings == | |||
Some of the settings used to configure the behavior of emails sent when Bodhi comments are sent by AutoQA require a bit more explanation than what is contained in {{filename|autoqa.conf}}. | |||
=== States === | === States === | ||
| Line 68: | Line 66: | ||
| FAIL | | FAIL | ||
|} | |} | ||
=== Koji Tags and Expected Tests === | === Koji Tags and Expected Tests === | ||
Since upgradepath is only run on packages in updates or updates-pending, it isn't run on packages in updates-testing. This means that the expected tests change depending on how packages are tagged. | Since upgradepath is only run on packages in updates or updates-pending, it isn't run on packages in updates-testing. This means that the expected tests change depending on how packages are tagged. | ||
= Supported releases and repositories = | |||
[https://fedorahosted.org/autoqa/browser/conf/repoinfo.conf {{filename|/etc/autoqa/repoinfo.conf}}] | |||
This file lists Fedora releases that will be tested and also links them to their YUM repositories. | |||
This file needs to be periodically updated to keep track of currently supported releases. Read more at [[How to update AutoQA repoinfo.conf]]. | |||
= FAS account = | |||
[https://fedorahosted.org/autoqa/browser/conf/fas.conf {{filename|/etc/autoqa/fas.conf}}] | |||
[[Account System|FAS]] account is needed for AutoQA to be able to send comments with test results to [[Bodhi]]. The account is configured here. | |||
= Apache web server = | |||
[https://fedorahosted.org/autoqa/browser/conf/autoqa-apache.conf {{filename|/etc/httpd/conf.d/autoqa.conf}}] | |||
This is AutoQA's apache configuration file now used for custom 404 page. | |||
[https://fedorahosted.org/autoqa/browser/watchers/git-post-receive/autoqa-git-hook.conf {{filename|/etc/httpd/conf.d/wsgi.conf}}] | |||
The <code>git-post-receive</code> watcher relies on WSGI. Support for wsgi is provided by {{package|mod_wsgi}} and it must be manually enabled in the provided Apache configuration file. | |||
= YOURLS shortening service = | |||
[https://fedorahosted.org/autoqa/browser/conf/yourls.conf {{filename|/etc/autoqa/yourls.conf}}] | |||
AutoQA supports [http://www.yourls.org/ YOURLS] shortening service to shorten test results URLs. This feature is optional and you don't need to configure it. If you decide to use it, this configuration serves for YOURLS integration into AutoQA. | |||
Read more about YOURLS installation at [[Install and configure YOURLS for AutoQA]]. | |||
= Log rotation = | |||
[https://fedorahosted.org/autoqa/browser/conf/logrotate.d/autoqa {{filename|/etc/logrotate.d/autoqa}}] | |||
This is the definition file how often and which way should the AutoQA log files be rotated. The log files are placed at {{filename|/var/log/autoqa/}}. | |||
[[Category:AutoQA]] | [[Category:AutoQA]] | ||
Revision as of 10:49, 28 November 2011
Most of the configurable settings in AutoQA are well documented in the comments of the configuration files. Here is the list of AutoQA's configuration files and some further information that wouldn't fit in the config files themselves.
General configuration
This is the main configuration file where all the general settings are available.
Bodhi Comment Email Settings
Some of the settings used to configure the behavior of emails sent when Bodhi comments are sent by AutoQA require a bit more explanation than what is contained in autoqa.conf.
States
The possible states of a test or an update as used here are PASS, FAIL, INCOMPLETE or NOTRUN.
Test State Change
A single test can change state that may or may not affect the update state as a whole. An example of this would be an updated package that changes test results from FAIL to PASS.
Update State Change
This type of state change is when the update as a whole would change from PASS to FAIL or FAIL to PASS.
Example where overall result changes from FAIL to PASS:
| Run | Test Result | Overall Result | ||
|---|---|---|---|---|
| depcheck 32bit | depcheck 64bit | upgradepath | ||
| Previous | PASS | PASS | FAIL | FAIL |
| Current | PASS | PASS | PASS | PASS |
Example where overall result does not change:
| Run | Test Result | Overall Result | ||
|---|---|---|---|---|
| depcheck 32bit | depcheck 64bit | upgradepath | ||
| Previous | PASS | FAIL | FAIL | FAIL |
| Current | PASS | FAIL | PASS | FAIL |
Koji Tags and Expected Tests
Since upgradepath is only run on packages in updates or updates-pending, it isn't run on packages in updates-testing. This means that the expected tests change depending on how packages are tagged.
Supported releases and repositories
This file lists Fedora releases that will be tested and also links them to their YUM repositories.
This file needs to be periodically updated to keep track of currently supported releases. Read more at How to update AutoQA repoinfo.conf.
FAS account
FAS account is needed for AutoQA to be able to send comments with test results to Bodhi. The account is configured here.
Apache web server
This is AutoQA's apache configuration file now used for custom 404 page.
The git-post-receive watcher relies on WSGI. Support for wsgi is provided by 
mod_wsgi
YOURLS shortening service
AutoQA supports YOURLS shortening service to shorten test results URLs. This feature is optional and you don't need to configure it. If you decide to use it, this configuration serves for YOURLS integration into AutoQA.
Read more about YOURLS installation at Install and configure YOURLS for AutoQA.
Log rotation
This is the definition file how often and which way should the AutoQA log files be rotated. The log files are placed at /var/log/autoqa/.