On Mon, Apr 10, 2017 at 01:29:32PM +0200, Kamil Paral wrote: > > > > Yes and no. The base image we build today only contains > > > components from one module, Base Runtime, however, that > > will definitely change for F27 (and possibly even for F26). > > We expect to use components from composes made of multiple > > different modules. > > > > Therefore I'm more interested in "integration level" type of > > tests rather than testing modules in isolation. > > > > OK, in that case we could help you create a "generic" task for Taskotron > that gets triggered every time there's a new Boltron image built (the build > system would need to send a fedmsg from which we can detect this) and the > Taskotron task would then download the image and run your test suite, then > report results to ResultsDB. There are no existing similar tasks yet > (testing docker images), at least in Taskotron. Ok, thank you. This was helpful. As was probably obvious from the initial mail, I don't really know what tool actually builds the image, so no idea what messages it currently does or doesn't emit :) Will dig into that some more and get back to you guys. P
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
