[mapguide-internals] MapGuide RC3 Delayed - Fusion Map tips are broken

[Trevor Wekel]

Hello Ivan,

The builds are not fully automated yet.  I have some batch/shell scripts which do a lot of the work.  I still need to run the scripts and do some validation on the build before posting them.  Here's a rough breakdown by platform:

Windows 64 bit: http://trac.osgeo.org/mapguide/browser/branches/2.2/Installer/scripts/buildmgx64.bat does most of the work.  The script is quite dumb and does not break nicely on errors.  Some manual intervention is occasionally needed.  The full build from svn export to installer takes approximately two hours.  The build script is tailored to the directory structure and setup on the build machine.  It takes a while to set up a build machine with the entire toolset needed to perform the build (Visual Studio, Perl, Wix, doxygen, graphviz, Fdo binaries, etc).

Windows 32 bit: http://trac.osgeo.org/mapguide/browser/branches/2.2/Installer/scripts/buildmgx86.bat.  Same comments as the 64 bit Windows build and the full build also takes roughly two hours.

CentOS 5 32 bit: http://trac.osgeo.org/mapguide/browser/branches/2.2/Installer/scripts/build.sh does the bulk of the work.  Fdo has to be installed first as well as various distro packages.  The build script is also dumb and needs some beefed up error checking.  The full build takes somewhere between 3 and 4 hours assuming everything goes ok.

Ubuntu 9 32 bit:  http://trac.osgeo.org/mapguide/browser/branches/2.2/Installer/scripts/dpkgmapguide.sh.  This one is ugly.  Since MapGuide 2.2 does not compile easily on Ubuntu 9, I have to manually copy the CentOS 5 binaries to an Ubuntu box.  Careful symlinking can get around the "missing" distro libs that the CentOS bins are expecting.  We have some basic "deb" packaging implemented and it is a bit messy.  Hopefully we can move to native compilation for MapGuide 2.3.  Some of the third party libs that were preventing compilation on Ubuntu for MapGuide 2.2 have been upgraded.  The entire packaging process takes about an hour once the CentOS binaries have been loaded.

So the entire build process is roughly two or three hours of my time assuming everything goes smoothly.  Then I need to validate it.  Installing MapGuide, loading the Sheboygan data set, and performing some interactive testing (pan/zoom/select/buffer for Fusion and Basic) takes roughly an hour per platform.  This ends up being approximately four hours of manual testing effort.

The total process is roughly one person day spread over a two day period.  It will be even more involved when we add 64 bit for CentOS and Ubuntu.

The Windows and CentOS builds could be fully automated using Cruise Control.  I expect it will be somewhere around 1 man week of effort to get this up and running.

If I was billing for this time, a single build would cost $1000 and build automation using Cruise Control would be somewhere around $5000 to implement.  This is exclusive of the hardware and software costs needed to maintain the build infrastructure. To date, the MapGuide Open Source project has received approximately $1000 in sponsorships and donations.
 
Regards,
Trevor

-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Ivan Milicevic
Sent: February 8, 2011 7:04 AM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] MapGuide RC3 Delayed - Fusion Map tips are broken

Hello Trevor,

It's little offtopic, I'm wondering how long does the process of building binaries?

-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Trevor Wekel
Sent: Tuesday, February 08, 2011 1:50 AM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] MapGuide RC3 Delayed - Fusion Map tips are broken

Hi Mike,

The fix seems to work.  I am starting the builds again.


Thanks!
Trevor

-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Michael Adair
Sent: February 7, 2011 7:36 AM
To: mapguide-internals at lists.osgeo.org
Subject: Re: [mapguide-internals] MapGuide RC3 Delayed - Fusion Map tips are broken

Trevor,

I will have a look at that today.

Mike

On 06/02/2011 11:19 AM, Trevor Wekel wrote:
> Hello list,
>
> After spending most of the last few days reconfiguring the build infrastructure after hardware failure and building MapGuide 2.2:
>
> - Windows 32 bit
> - Windows 64 bit
> - CentOS 5 32 bit
> - Ubuntu 9 32 bit (based on CentOS 5 bins)
>
> I am "disappointed" to report that initial validation of the build using the sample Sheboygan map was not successful.  The Fusion tooltips seem to be broken.  Since tooltips are somewhat important, the build has been put on hold until someone (not me) had had a chance to fix the issue.
>
> http://trac.osgeo.org/fusion/ticket/433 Map tips are broken in branches/2.2
>
> Regards,
> Trevor
>
>
>
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
_______________________________________________
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

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