I'm not sure the process for posting on oVirt.org but I wouldn't mind at all. I was going to write one on my personal blog as well. I'll send an email in a few.

As for the tests, the unit tests are rspec and can run without a server. The acceptance tests were, in my mind, just going to be a bunch of directories, each with a vagrantfile specific to the test, such as one with specific CPU/ram, one with a bash provisioner, and the tests were going to be simple `bats` tests that vagrant up, vagrant halt, snapshot , restore from snapshot, etc and test error codes. Those will need a master but the tests would just be time consuming workflow specific assertions. Feel free to suggest something else, but that's what I had planned

On Sun, Feb 5, 2017, 8:17 AM Yaniv Kaul <ykaul@redhat.com> wrote:

On Feb 5, 2017 1:58 PM, "Marc Young" <3vilpenguin@gmail.com> wrote:

I see emails floating around about Jenkins.

Is there a public Jenkins, or possibly one that I can be invited to?
I just finished the vagrant provider and

Excellent news -  saw it on twitter!  

Can you send an email to the users mailing list about it? 

Perhaps even a blog post on ovirt.org? 

pushed it to rubygems and am
currently bringing up a new permanent oVirt server so that i can write
some acceptance tests, but having access to a Jenkins and a testable
oVirt setup would save me a ton of time.

I'm sure it can be integrated nicely to ovirt-system-tests. Let me think about it for awhile. 

Y. 

_______________________________________________
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

_______________________________________________
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel