Fedora package maintainers, want test results?

For a some time now, automated tests have been running against Fedora package builds thanks to the AutoQA post-koji-build watcher.  The current tests are by no means exhaustive, but they do provide some level of automated feedback for those interested in a quick sanity check of their package builds.  As a proof-of-concept, and before the spiffy results database is online, all test results are sent to the autoqa-results mailing list.

A few weeks back, Seth Vidal proposed several changes to allow package maintainers to sign-up for test results by mail.  We all get a lot of email as it is, so this certainly isn’t the long-term option.  However, it is an option for package maintainers who want test results emailed directly to them for review.

So, if you want to sign-up for email notification of test results (includes rpmlint, rpmguard and, if applicable, initscripts) whenever you build new packages:

  1. Using your FAS credentials, login to fedorapeople.org  (for assistance, see access instructions)
  2. Sign-up by running the command  autoqa-optin with appropriate options.  For example, to enable test emails for pykickstart for all rawhide and Fedora 14 builds, you would run:
    # autoqa-optin pykickstart devel F-14
    Opted into autoqa results for pykickstart of devel release
    Opted into autoqa results for pykickstart of F-14 release

To query which releases are configured for test result notification, you can run the autoqa-optin script with just a package name.  For example:

# autoqa-optin yum
yum opted in for releases:

Available Releases to be opted into:


3 responses to “Fedora package maintainers, want test results?

  1. Daniel Berrange

    What RPM is the autoqa-optin command located in ? I’m not able to find it in Fedora 13 so far…

  2. Good question. After consulting with the Fedora infrastructure team, the autoqa-optin script is not packaged and only available on Fedora infrastructure systems. The script is tailored to run only on ‘fedorapeople.org’. I’m not sure if it makes sense to package, but we’ve talked about adding it to a ‘scripts/’ or ‘contrib/’ directory in the autoqa project.

  3. Pingback: AutoQA 0.5.0 released « Kparal's Fedora Blog

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s