On Mon, 3 Oct 2016 20:21:42 +0000 Zbigniew Jędrzejewski-Szmek <zbys...@in.waw.pl> wrote:
> On Mon, Oct 03, 2016 at 01:50:33PM -0600, Tim Flink wrote: > > One of the features for Taskotron that we've been planning since the > > beginning was a way for contributors to maintain their own automated > > tasks/tests which would be run during a package's lifecycle. > > > > I'm happy to say that we're almost to this milestone and wanted to > > get some feedback from devel@ on the specifics of what we're > > planning WRT where these automated tasks will be stored and the > > execution modes that we're planning to support. Our current plan is > > written up at: > > > > https://phab.qadevel.cloud.fedoraproject.org/w/taskotron/new_distgit_task_storage_proposal/ > > > > Sounds reasonable. > > How does the environment in which those tasks are run look? > Would it be possible for example to run a test which launches > a qemu VM to test stuff that requires a functional installation > and a reboot? It will be a VM running updated Fedora. Rebooting during execution isn't something we explicitly support but it has been requested before. I've filed an RFE ticket to track the feature: https://phab.qadevel.cloud.fedoraproject.org/T849 Our intent is to get this into place before F26 knowing full well that we're going to be missing features that some folks will need. We're not quite stupid/arrogant enough to pretend that we know what's needed to support all the different kinds of tasks that people will want to run. Instead of guessing what people need, we're intending to start adding features once there are use cases from people who know the components they work on FAR better than we do. Tim
pgp1NTb7quQ1A.pgp
Description: OpenPGP digital signature
_______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
