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

[Hans-Christoph Steiner]

Steven Chamberlain:
> Hans-Christoph Steiner wrote:
>>>>> As for http_proxy, env vars are not cleared, but then also not sent to
>>>>> the VM, where apt is running. The http_proxy is for .deb caching,
>>>>> right? Since that's already happening locally, so this shouldn't be
>>>>> using much bandwidth.
>>>
>>> Does that mean there's no proxy in use by the VM? That's not nice.
>>
>> I don't know if VirtualBox automatically uses proxies from an env var.
>> The most manageable thing probably would be to force all of the
>> VirtualBox's net traffic through a SOCKS proxy.  [...]
> 
> Sorry, I didn't read the whole thread, but - is this just for APT
> downloads within the VM?  Can you just create the VM with a custom file
> in /etc/apt/apt.conf.d/, like I have a file called 10proxy:
> 
> Acquire::http::Proxy "http://aptcache:3128/";
> 
> Regards,

Sure, its all possible, but given that this jenkins job is about fully
scripted, reproducible creation of a VM instance for running the F-Droid
buildserver, it would be a chunk of work to get that working properly
because it has to be scripted and tested.  And it would only provide
tiny benefits since this setup already does a lot of caching.  We don't
even yet have a complete build on this jenkins setup.  So my request is:
first, let's get it actually working, then think about optimizations.

FYI, this script is running reliably on Guardian Project's jenkins box.

.hc