I just had the "aha" moment and i"m sorry. I think I'll take a nap.
In jenkins the local directory is mounted into the container in order to
get the code there. This includes the `.kitchen` dir which has all the
state information. So the 2nd run of `kitchen ...` will have the dir and
try to use the
This is where the ID is retrieved and stored:
https://github.com/myoung34/vagrant-ovirt4/blob/master/lib/vagrant-ovirt4/action/create_vm.rb#L79
workflow is: create, wait til disks are OK, wait until vm status is "down",
create network interfaces[1], start vm[2], wait until up[3]
[1]
https://githu
On 03/07/2017 06:06 PM, Marc Young wrote:
> Completely isolated docker containers. Jenkins basically runs two
> separate calls to docker...
>
> [vagrant-1.9.1] $ docker run -t -d -u 997:994 -v
> /opt/gemcache:/opt/gemcache -w
> /var/lib/jenkins/workspace/oung34_vagrant-ovirt4_PR-79-7BRKVM5TQ
Completely isolated docker containers. Jenkins basically runs two separate
calls to docker...
[vagrant-1.9.1] $ docker run -t -d -u 997:994 -v
/opt/gemcache:/opt/gemcache -w
/var/lib/jenkins/workspace/oung34_vagrant-ovirt4_PR-79-7BRKVM5TQ5BGPECFMXYIEOYZOICCET4GY37WXT4D65NSV4F5TADQ
-v
/var/lib/jen
On 03/07/2017 05:42 PM, Marc Young wrote:
> I've been fighting this for roughly two days and I'm starting to think
> that possibly it's not my code but an interaction with the server.
>
> I'm using test-kitchen[1] with the kitchen-vagrant[2] driver to spin up
> vagrant machines and run tests again
I've been fighting this for roughly two days and I'm starting to think that
possibly it's not my code but an interaction with the server.
I'm using test-kitchen[1] with the kitchen-vagrant[2] driver to spin up
vagrant machines and run tests against them. I'm using Jenkins to run
kitchen in contain
