Greetings,
Just a heads up in case anyone is interested in the autoqa package
repository. I just completed updating builds for AutoQA and it's
dependencies for fc13, fc12 and el5. Be advised, whenever upgrading
autotest, you may need to run database migration.
Information on using the package repository is available in either the
AutoQA [1] or Autotest [2] setup guides.
Thanks,
James
[1] https://fedoraproject.org/wiki/Install_and_configure_autoqa
[2] https://fedoraproject.org/wiki/Install_and_configure_autotest
----- "Kamil Paral" <kparal(a)redhat.com> wrote:
> I have been reading through instructions how to add new autotest
> clients [1] and I've seen a link there pointing to non-existent
> page "Managing autotest labels". So I created it, here it is:
>
> https://fedoraproject.org/wiki/Managing_autotest_labels
I have changed i686 label to i386 label. Currently there's a lot
of inconsistency between these labels throughout Fedora, but in
the end i386 seemed to me like a better option. i686 is used
mainly for RPM package names, i386 seems to be used in most of
all other places (most notably in file paths of Fedora composes).
Just a convenience change.
#32: Add autotest rpm dependencies into fedora infrastructure repo
-----------------------------+----------------------------------------------
Reporter: jlaska | Owner: jkeating
Type: task | Status: closed
Priority: major | Milestone: Packaging, Review, & Deployment
Component: infrastructure | Version: 1.0
Resolution: invalid | Keywords:
-----------------------------+----------------------------------------------
Changes (by jlaska):
* status: new => closed
* resolution: => invalid
Comment:
Nothing to track in this ticket anymore. A package repository is
available for those interested in testing. Instructions available at
https://fedoraproject.org/wiki/Install_and_configure_autotest and
https://fedoraproject.org/wiki/Install_and_configure_AutoQA
All packages need to be packaged for Fedora, this is a requirement by the
infrastructure team. Packaging of autoqa dependencies will be tracked in
a different ticket for each package.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/32#comment:6>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
#51: Docs for autoqa/autotest admins
------------------------+---------------------------------------------------
Reporter: wwoods | Owner: jlaska
Type: task | Status: new
Priority: major | Milestone: Packaging, Review, & Deployment
Component: docs/wiki | Version: 1.0
Resolution: | Keywords:
------------------------+---------------------------------------------------
Old description:
> Write some wiki documentation about common tasks for autoqa/autotest
> admins. We should be providing this info so the Infrastructure team can
> help manage the AutoQA systems.
>
> Some topics to cover:
>
> * Managing Test Hosts
> * Adding new hosts
> * Rebuilding broken hosts
> * Marking a rebuilt host ready for new tests
> * Managing tests
> * Manually triggering hooks
> * Re-running specific tests from the CLI
> * Cloning jobs in the Web UI
New description:
Write some wiki documentation about common tasks for autoqa/autotest
admins. We should be providing this info so the Infrastructure team can
help manage the AutoQA systems.
Some topics to cover:
* Managing Test Hosts
* Adding new hosts
* Rebuilding broken hosts
* Marking a rebuilt host ready for new tests -
* Autotest-server upgrade procedure
* Managing tests
* Manually triggering hooks
* Re-running specific tests from the CLI
* Cloning jobs in the Web UI
Comment (by jlaska):
Current documentation status. Much of this will change/depend on how the
system is deployed in Fedora infrastructure.
* Managing Test Hosts
* Adding new hosts -
https://fedoraproject.org/wiki/How_to_add_autotest_clients
* INPROGRESS - need to document system labels used (pending outcome
from ticket#184)
* Rebuilding broken hosts -
https://fedoraproject.org/wiki/How_to_fix_failed_autotest_clients
* COMPLETE
* Marking a rebuilt host ready for new tests -
https://fedoraproject.org/wiki/How_to_fix_failed_autotest_clients
* INPROGRESS - needs update to autotest-0.12.0 recovery procedure
* Autotest-server upgrade procedure
* INCOMPLETE
* Managing tests
* Manually triggering hooks
* INCOMPLETE
* Re-running specific tests from the CLI
* INCOMPLETE
* Cloning jobs in the Web UI
* INCOMPLETE
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/51#comment:3>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
#197: New test: "See also" validity in man pages
--------------------+-------------------------------------------------------
Reporter: kparal | Owner:
Type: task | Status: new
Priority: major | Milestone: Future test cases
Component: tests | Version: 1.0
Keywords: |
--------------------+-------------------------------------------------------
Ivana Varekova has a script created that is able to check man pages
whether the references in "See also" section are valid or whether they
point to inexistent tools. This would be a great new test case we could
incorporate into AutoQA.
The test would be probably run with post-koji-build hook. Our task is to
create a AutoQA wrapper script for her test. Ivana is also open to
modifications - for example she currently installs the package to check
it, but it is possible to change this behaviour and check it just from
extracted rpm, which is more suitable for our needs. We will need to
inspect the script and propose such modifications.
Please Ivana, attach your script here or provide a link where we can find
it. Thanks.
PS: Ivana concentrates at man-pages checking, so if we ever want to create
some other tests concerning man-pages, we should certainly contact her in
advance, she might have already implemented it.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/197>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project