On Mon, Apr 10, 2017 at 11:09 AM, Petr Šabata <contyk@xxxxxxxxxx> wrote:
Is the docker image the same thing as a "module"? We should have some support for testing modules in Taskotron soon. I assume it should be similar to RPM dist-git testing (PoC running now):For the Boltron deliverable (the Modularity thing) we would like
to build, test and ship a Base Runtime / Boltron docker base
image. Now, the whole process is still not entirely clear to me
so I'll just go ahead and briefly describe how I think it works:
1. You build your RPM components in koji
2. You have your components appear in a compose
3. You write a kickstart file that creates your base image
4. You have your kickstart file included in fedora-kickstarts
5. You file a releng ticket to run your kickstart file against
your compose regularly
6. Something processes the kickstart file somewhere and builds
the base image (is this imagefactory in koji? is this OSBS?
is this, er, pungi?)
7. The image is then tested somehow, hopefully
8. The image is then pushed to Fedora registry
Feel free to correct or clarify any of the points above.
Anyhow, the main point of this mail are the last two items on
that list. How do we test docker images, if at all? Do we only
run some sanity tests or is there a way to test their contents
as well?
https://fedoraproject.org/wiki/Taskotron/DistGitTasks
So a new module gets built, we look into distgit and run all tests that are present for that module.
Jan Scotka is even working on a framework to make module testing easier:
https://pagure.io/modularity-testing-framework
Jan Scotka is even working on a framework to make module testing easier:
https://pagure.io/modularity-testing-framework
which can be used in conjunction with Taskotron (some easy-to-use integration coming in the near future, hopefully).
I'm somewhat out-of-date on current status of things, perhaps Tim Flink can add more insight here.
_______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
