Hi Volker

Does that allow scheduling sequential builds on multiple virtual (OK,
containers) buildslaves with different IPs and hostnames on one physical
host?

Regards,
Jan

On 28 March 2015 at 11:04, Volker Braun <vbraun.n...@gmail.com> wrote:

> Thats easy, Buildbot has locks to control scheduling, I've already set it
> up so that it only build/tests one sage at any given time on a buildslave.
>
>
> On Saturday, March 28, 2015 at 8:31:39 AM UTC+1, Jan Groenewald wrote:
>>
>> Hi Volker
>>
>> If buildbot could schedule sequential runs instead of parallel, I could
>> supply many LXC buildslave instances for Debian/Ubuntu.
>>
>> 32bit and 64bit
>> Ubuntu 12.04, 14.04, and latest.
>> Debian stable, testing, unstable.
>>
>> Regards,
>> Jan
>>
>> On 28 March 2015 at 01:17, Volker Braun <vbrau...@gmail.com> wrote:
>>
>>> With Sage-6.6 there will also be the usual 32-bit builds again.
>>>
>>> Our buildbot makes the binaries, and it would be great if we could
>>> increase coverage. Buildbot also has support for libvirt to build/run
>>> virtual machines, though we currently don't make use of it. Another
>>> possibility would be to run buildbot slaves in docker and have buildbot
>>> schedule them so that only one is active at a time.
>>>
>>>
>>> On Friday, March 27, 2015 at 10:23:30 PM UTC+1, Thierry
>>> (sage-googlesucks@xxx) wrote:
>>>>
>>>> Hi,
>>>>
>>>> there is currenlty no 32-bits binary for 6.5 on the mirrors, and only a
>>>> single one for 6.4.1 that runs on an unmaintained Ubuntu release
>>>> (13.04).
>>>> However, those are still needed for quite a lot of users i met (not
>>>> only
>>>> users with old computers but also those that run i686 kernel on a 64
>>>> bits
>>>> material, this was the default choice for downloads on ubuntu website
>>>> until quite recently).
>>>>
>>>> Hence i wrote a buildchain (in bash, sorry) to automatically spawn,
>>>> boot,
>>>> upgrade a qemu VM for each maintained Ubuntu/Debian release (precise,
>>>> trusty, utopic (and vivid soon) / wheezy, jessie, sid), and build Sage
>>>> on
>>>> it.
>>>>
>>>> To ensure wide compatibility, the qemu-lated processor is Pentium III
>>>> (Katmai) and the builds use the #17806 patch to allow SAGE_FAT_BINARY
>>>> to
>>>> work.
>>>>
>>>> http://lipn.univ-paris13.fr/~monteil/hebergement/sage/binaries/
>>>>
>>>> Please do whatever could be useful with that (try it, mirror it, PPA
>>>> it,...).
>>>>
>>>> The buildchain should be able to build all 64 bits as well, but Sage
>>>> 6.6
>>>> is at the corner so i will wait for its release and for feedback about
>>>> the
>>>> current builds.
>>>>
>>>> Ciao,
>>>> Thierry
>>>>
>>>>
>>>>  --
>>> You received this message because you are subscribed to the Google
>>> Groups "sage-devel" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to sage-devel+...@googlegroups.com.
>>> To post to this group, send email to sage-...@googlegroups.com.
>>> Visit this group at http://groups.google.com/group/sage-devel.
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>>   .~.
>>   /V\     Jan Groenewald
>>  /( )\    www.aims.ac.za
>>  ^^-^^
>>
>  --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-release.
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
  .~.
  /V\     Jan Groenewald
 /( )\    www.aims.ac.za
 ^^-^^

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Reply via email to