On 08/15/2011 01:53 PM, Kent A. Reed wrote:
> I have been lurking about emc for a very long time. I've mostly made my
> presence known through my off-the-cuff (some would say snarky) remarks
> on the emc-users list. As much as I would like to, life has prevented me
> from making substantive contributions to the development of emc2.
>
> Andy Pugh's recent mention of the emc2 buildbot suggests a way for me to
> give something back. I have been playing with Amazon's cloud computing
> services. It would be pretty trivial for me to put up a buildbot in
> support of emc2 2.6 and above.
>
> However, I couldn't figure out from the available material whether yet
> another buildbot is needed, and, if it is, what O/S, configuration,
> etc., is most needed.

The buildbot is currently building the 2.4 and 2.5 branches, and master 
(aka 2.6).  It's building these branches on all our currently supported 
platforms (hardy and lucid 32-bit realtime, hardy 64-bit realtime, and 
hardy and lucid 32-bit and 64-bit sim).

I currently run the buildmaster and all the buildslaves.  It's sometimes 
convenient to have all of those machines under my control, because it 
makes maintenance and upgrades easy.

If you want to add a new platform/configuration and add a buildslave for 
it, that'd be fine.  There may be some maintenance work required to get 
emc2 to run on that new platform.

If you want to run a buildslave for one of the currently supported 
platforms/configurations on your hardware, that'd be fine too.


-- 
Sebastian Kuzminsky


------------------------------------------------------------------------------
uberSVN's rich system and user administration capabilities and model 
configuration take the hassle out of deploying and managing Subversion and 
the tools developers use with it. Learn more about uberSVN and get a free 
download at:  http://p.sf.net/sfu/wandisco-dev2dev
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to