[Seaside-dev] [Seaside] Build Process
dhenrich at vmware.com
Sat Mar 5 21:09:40 UTC 2011
More often than not the integration of changes from the Pharo version of Seaside to GemStone involves manual intervention by a developer to resolve. So automation on that from would require my attention anyway ...
I have been threatening to convert the functional tests to automated tests, but have just not had the cycles to do so ... it would be very useful.
I _am_ spending time on the MetacelloBrowser ... when that tool is ready, the Seaside developers could use the MetacelloBrowser to update the configs for Grease and Seaside rather than waiting me to find time to do it ...
Oh and let's see, I think there should be a hudson build for just Grease since one of the issues this time around would have been exposed by a Grease only build ... using a configuration to load Grease would have exposed the problem as well, but I know that Grease is being used in other projects besides Seaside, so independent testing there would be useful...
On Mar 5, 2011, at 9:27 AM, Avi Shefi wrote:
Functional tests cannot be automated because they are output-driven. One could test them using Selenium or WebTester, however things like HTML5 functional tests are not possible because they rely on browsers implementations.
Regarding local files - it's not what bothers me. I can live with local files, even though I believe that dangling files are a recipe for information loss. Here are two key points which derive from this:
- Why not create a configuration for the Hudson build server to fetch specific Monticello packages, by versions? This would eliminate the need to not commit to Monticello while building a version.
- How can we automate the process of testing Seaside via the different platforms? If we have a uniform build process, maybe this can encourage other dialects to maintain their ports to Seaside?
- Is the OneClick distribution automated, or is it built manually?
We can make the build process less involved.
On Sat, Mar 5, 2011 at 7:16 PM, Philippe Marschall <philippe.marschall at gmail.com<mailto:philippe.marschall at gmail.com>> wrote:
2011/3/5 Avi Shefi <avishefi at gmail.com<mailto:avishefi at gmail.com>>:
> Hi there,
> Having watched the build process for the first time, it looks like there are
> some complicated steps involved.
> I have read the MakeRelease document on the Wiki, and I wondered if there's
> room for further improvements/automation ?
The functional tests are not automated.
> If there's one issue that particularly captured my attention, it was the
> fact that we had to stop further commits to the repository during the build.
> I'd love to hear your thought about this.
I just make commits that should not go into the release to a local
file repository. Works fine.
seaside-dev mailing list
seaside-dev at lists.squeakfoundation.org<mailto:seaside-dev at lists.squeakfoundation.org>
More information about the seaside-dev