I'm trying to follow the following guide:
Let's say I've done the following:
$ fedpkgclone gzip
$ cd gzip/tests/
Now I want to run the tests in Docker. The guide says:
> Try running this example test against an Atomic Host or Docker
Container. It should pass.
"Docker Container" leads to:
So I've done:
$ export TEST_SUBJECTS=docker:docker.io/library/fedora:26
$ ansible-playbook --tags=container tests.yml
I see a lot of cows (cute), yet the error is:
> "Destination /usr/local/bin not writable"
It's also amazingly fast, so I think no Fedora 26 docker image is being
pulled in. I don't think docker is invoked here at all.
What piece am I missing?
With a couple of guys we've been discussing a slightly
backward-incompatible change in the way how fmf is handling the root
of the metadata tree. In short we suggest to clearly define where the
metadata tree starts by including an ".fmf" directory:
This approach is very similar to what git does and should allow us to
request metadata from inside the directory structure without always
having to specify the root. If you have any concerns or suggestions
regarding this change, please join our discussion on GitHub.
Following the first set of essential attributes for the Flexible
Metadata Format we are starting to discuss a new attribute which
could be used to specify environment for which a test case is
relevant. The first draft is available on the Metadata wiki:
This new attribute should help us to better share test code
between Fedora and RHEL as it allows to store and maintain test
code at a single place and run for all appropriate environments.
Feedback is welcome.