twisted-buildslaves team mailing list archive

[Tobias Oberstein <tobias.oberstein@xxxxxxxxxx>]

Hi,

we operate 2 FreeBSD buildslaves, one running FreeBSD 8.2, and one running FreeBSD 9.1.

****
I would like to retire the 8.2 (listed under "supported"), and keep the 9.1, and make the latter "supported" (currently it's only listed under "unsupported")
****

This one I'd like to retire:
Slave: http://buildbot.twistedmatrix.com/buildslaves/bot-tobias-1
Builder: http://buildbot.twistedmatrix.com/builders/freebsd-8.2-i386

The other one we operate runs FreeBSD 9.1:
Slave: http://buildbot.twistedmatrix.com/buildslaves/tavendo-freebsd-9.1-amd64
Builders:
http://buildbot.twistedmatrix.com/builders/freebsd-9.1-amd64-python2.7
http://buildbot.twistedmatrix.com/builders/freebsd-9.1-amd64-pypy2.0

This newer one is 100% green on the recently merged Twisted 13.2 release:
http://buildbot.twistedmatrix.com/builders/freebsd-9.1-amd64-python2.7/builds/198

I'd like to bring that slave up FreeBSD 9.2, and continue to run a

- CPython 2.7 builder
- PyPy builder

For the latter I want that same host to operate as a buildslave for the PyPy project _also_.

This will allow the Twisted/PyPy builder to run the very latest, nightly PyPy.

Right. Normally running the latest nightly (as eg for CPy) wouldn't make sense for a Twisted slave.

However, PyPy is moving fast, and there might be issues that pop up in Twisted trial that needs fixing in PyPy.

Operating a Twisted and PyPy buildslave on the _same_ host will make that fixing easier.

The host will need to get at least 4GB RAM and generally be beefed up - it's a VM anyway, so I can control that.

So: I'd like to ask: are there any objections against above?

And if not: could we promote the 9.1 to "supported" as a first action?

Thanks!
/Tobias