[Biopython-dev] Volunteer buildslave machines? e.g. Windows & 32 bit Linux

Peter Cock p.j.a.cock at googlemail.com
Mon Mar 24 11:57:14 UTC 2014


Hello all,

Tiago and I have been looking after a range of machines
covering different operating systems and Python versions,
running as volunteer buildslaves for Biopython using buildbot:
http://testing.open-bio.org/biopython/tgrid

Does anyone else have a lab/home server which could be
setup to run nightly Biopython tests for us via buildbot?
Ideally the machine needs to be online overnight (European
time) when the server is currently setup to schedule tests:

http://www.biopython.org/wiki/Continuous_integration

Our elderly 32 bit Linux desktop which has been running
as a Biopython buildslave for the last few years is finally
failing (hard drive problem).

I would particularly like to see new buildslaves for:

* 32 bit Linux
* 64 bit Windows
* Windows 7 or 8 (we have a 32 bit XP machine)

If you think you might be able to help, the first hurdle is
verifying you can checkout Biopython from github, and
then compile the source (this is non-trivial on Windows,
especially for 64 bit Windows).

Note that this is separate from the continuous integration
testing done for use via TravisCI whenever the GitHub
repository is updated - this is very useful but currently
only covers Linux:
https://travis-ci.org/biopython/biopython/builds

The key benefit of the buildbot server is cross platform
testing - but this requires a range of volunteer machines.

Thanks,

Peter



RE: http://lists.open-bio.org/pipermail/biopython-dev/2014-March/011158.html

On Tue, Mar 18, 2014 at 1:15 PM, Peter Cock <p.j.a.cock at googlemail.com> wrote:
> On Wed, Mar 12, 2014 at 3:10 PM, Tiago Antao <tra at popgen.net> wrote:
>> Hi,
>>
>> I have a docker container ready (save for a few applications). Simple
>> usage instructions:
>>
>> ...
>>
>> Tiago
>
> Is this a 32 or 64 bit VM, or either?
>
> I'm asking because we may want to source a replacement
> 32 bit Linux buildslave - the hard drive in the old machine
> we've been using is failing, and it is probably not worth
> replacing.
>
> Peter



More information about the Biopython-dev mailing list