[mapguide-internals] MapGuide Open Source 2.1 - where isthecontinuous integration system ????

[Trevor Wekel]

I have a PayPal account already set up.  I also have an ESX Server box with 4 cores, 8 GB ram, and approximately 250GB of disk running in my basement.  This should be enough hardware to run build VMs for a few distros.  My outgoing internet connection is a bit slow but it should be ok for occasional remote access.

I think BuildBot will also work for Windows.  It may be possible to set up daily builds and weekly "promotes" using BuildBot.

Thanks,
Trevor



________________________________________
From: mapguide-internals-bounces at lists.osgeo.org [mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Jason Birch [Jason.Birch at nanaimo.ca]
Sent: Thursday, November 13, 2008 4:37 PM
To: MapGuide Internals Mail List; MapGuide Internals Mail List
Subject: RE: [mapguide-internals] MapGuide Open Source 2.1 - where      isthecontinuous integration system ????

Hey Tom,

I'm not sure that the community has the mechanisms in place (funding, etc) to do it right.  I guess Trevor could set up a PayPal account :)  Perhaps we need to look at joining the OSGeo project sponsorship program?  Or investigating whether we can get some support at Telascience, though their hardware seems a bit stressed these days.

If this turns out to be beyond our current capabilities, I don't think it would necessarily be bad to leave packaging in one individual's hands, as long as all of the required files to do so are in SVN.  Many open source projects with limited resources operate this way.

What do we need?  I believe that Trevor's outlined this in previous emails, but lets flesh it out before putting it into an RFC:

-> Server Machines (VM) / OS
  - Windows 200x
  - Linux (at least one flavour)

-> Software
  - Windows:  Visual Studio Standard for builds, some kind of continuous build framework (can't remember what Trevor recommended here)
  - Linux: Buildbot?

-> Glue
  - Copies of existing scripts for command-line building in Windows (I've asked for these before, but I don't think they made it into SVN)
  - Description of current unit testing procedures
  - Documentation on files/keys/configuration/permissions required for Windows installer.  I don't think the InstallShield files will be of much help to anyone here, but could be surprised?  Worse case, I can reverse-engineer this from the 2.0 installer, but...
  - And of course time/effort from folks to get it all put together.  I'm happy to contribute where I can...

Am I missing anything?

Jason

_______________________________________________
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals