[Qa-jenkins-dev] setup up the fdroid build env (Re: pull request

[Holger Levsen]

Hi,

On Donnerstag, 11. Februar 2016, Hans-Christoph Steiner wrote:
> > I've now commited + deployed another attempt of fixing this. Triggering a
> > job run now…
> 
> Ok, we're back to where we were before with the fail on timeout.  My
> guess is that its trying to use an old broken instance.  Can you delete
> the old vagrant/VirtualBox setup?  Those both should now be totally
> self-contained in the jenkins job, and wiped on each build.  That is
> done like this:
> 
> rm -rf ~/.vagrant.d
> rm -rf ~/VirtualBox\ VMs
> rm -rf ~/.config/VirtualBox/

Doing so now. I'm wondering whether we want a job (which is never run 
automatically) for doing this more easily and reliable…
 
> Just be sure nothing else is using vagrant or VirtualBox, since this
> would delete all the settings and VMs!

there's nothing.

> If that fails, then we'll have to launch the VirtualBox GUI to see where
> the failure is. It'll work over X11 forwarding.

one potential difference between your and this setup which came to my mind: 
we're using jessie *without* systemd atm, because there was an issue with 
schroots. Are you using systemd or sysv?


cheers,
	Holger
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 828 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/qa-jenkins-dev/attachments/20160212/bad8bf01/attachment-0001.sig>