On Thu, Apr 13, 2017 at 9:05 PM, Frederic Lepied <flepied@redhat.com> wrote:
On Thu, Apr 13, 2017 at 8:20 PM, Stef Walter <stefw@redhat.com> wrote:
On 13.04.2017 13:56, Frederic Lepied wrote:
>
> On Thu, Apr 13, 2017 at 6:55 PM, Frederic Lepied <flepied@redhat.com
> <mailto:flepied@redhat.com>> wrote:
>
>     ok working on the page now.
>
>
>
> Here is the
> page https://fedoraproject.org/wiki/Changes/InvokingTestsControl . Let
> me know if anything is not clear or missing.

It's an interesting proposal.

But it seems that this requires a port of the autopkgtest to support
rpm/dnf? Is that already in progress somewhere? If not, I guess that's
the main thing that's missing?

Yes I have it working locally on my laptop. That's more a hack but it's working.
 

After that what are the specific commands, environment, and tasks that a
testing system uses to stage and invoke the tests. What kind of system
should those commands be invoked on?


Ok I'll add an example call to the wiki page.
 
Also missing is a complete functioning example of how the test is
described in dist-git. Preferrably with a link to a dist-git repo close
where you've stored the test, control file, and explain how to invoke it
on a current Fedora system.

 
Ok I have tried to describe the files in the example but I'll create a dist-git.


I have added a dist-git repo for the systemd example and we have also created a CI pipeline to demonstrate that a bad change is detected by the tests: https://softwarefactory-project.io/r/#/c/7495/ and you can also look at the details of the CI job: https://softwarefactory-project.io/jenkins/job/fedora-integration-test/7/console

How could I make people aware of this alternative choice? Should I contact those who have already voted? Or is there a way to let them know?

Thanks,
--
Fred