cri-o/contrib/test/integration
Chris Evich a30a118fe6 integration: Collect subject results
Add a playbook to pull down the integration and e2e testing
logs/xml.  By default they will appear in a 'artifacts' subdirectory
of wherever the ``results.yml`` playbook lives. If the ``$WORKSPACE``
env. var is set and non-empty, the subdirectory will be created
there instead.

Inside the ``artifacts`` directory, further sub-directories are created,
one for each subject's Ansible inventory name.  Within those
sub-directories are all the collected logs from that host.  In this way,
automation may simply archive the entire 'artifacts' directory to
capture the important log files.

(Depends on PR #935)

Signed-off-by: Chris Evich <cevich@redhat.com>
2017-09-28 14:05:25 -04:00
..
build Refactor the CRI-O test playbook to be more modular 2017-09-25 10:02:04 -07:00
callback_plugins integration: Add color + readable logging 2017-09-28 14:05:25 -04:00
ansible.cfg integration: Add color + readable logging 2017-09-28 14:05:25 -04:00
e2e.yml integration: Collect subject results 2017-09-28 14:05:25 -04:00
golang.yml Refactor the CRI-O test playbook to be more modular 2017-09-25 10:02:04 -07:00
main.yml Refactor the CRI-O test playbook to be more modular 2017-09-25 10:02:04 -07:00
results.yml integration: Collect subject results 2017-09-28 14:05:25 -04:00
system.yml Refactor the CRI-O test playbook to be more modular 2017-09-25 10:02:04 -07:00
test.yml Refactor the CRI-O test playbook to be more modular 2017-09-25 10:02:04 -07:00