<div dir="ltr"><font color="#330033"><font size="2"><font face="tahoma,sans-serif">re dedicated Hudson server - not needed. I thought the current server could be configured to have an artifact set under which you define a build based on specific versions of packages.<br>
<br>re Squeak & Pharo automation - sounds good, probably requires a Hudson plugin to make it happen.<br><br><br>Considering the responses I guess this is irrelevant at the present moment.<br><br>Avi.<br><br></font></font></font><div style="margin: 0pt;" name="sig_d41d8cd98f">
</div><div class="gmail_quote">On Sun, Mar 6, 2011 at 7:48 PM, Dale Henrichs <span dir="ltr"><<a href="mailto:dhenrich@vmware.com" target="_blank">dhenrich@vmware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><br>
On Mar 6, 2011, at 9:33 AM, Avi Shefi wrote:<br>
<br>
So we have two issues:<br>
1) Functional tests - can we, or can't we automate these? even if a large portion can be automated, how do you think this should be done?<br>
2) Should we have a Grease-only build? (Dale's suggestion)<br>
<br>
Regarding suspending the commits until a release - this works only because we're a small community :)<br>
I would definitely go for an automated build system which can handle both: (a) taking the latest package versions and doing nightly builds; and (b) defining a set of packages (or a Metacello configuration) for a release, and building it regardless of new commits (whether through a dedicated Hudson Seaside build, or some other mechanism).<br>
<br>
Another issue:<br>
Dale, Do we build/update/run a new release under each and every dialect manually?<br>
If it's manual, then maybe there's room for a script that fetches a Metacello configuration and runs Seaside tests against all dialects? or possibly a few dialect-specific scripts that automate this?<br>
<br>
</div>If someone created and maintained a hudson server that loaded the seaside configs for squeak I wouldn't have to do the manual builds/tests:)<br>
<br>
As I've mentioned before, the GemStone builds require manual merges and the other platforms don't use Monticello let alone Metacello:)<br>
<br>
Frankly I am still doing the metacello stuff manually so that I can experience the pain and improve metacello itself, as long as I keep learning from the experience I don't mind doing it manually ... but if there were more automation for building on the Squeak releases and the old Pharo releases, I wouldn't complain:)<br>
<font color="#888888"><br>
Dale<br>
</font><div><div></div><div>_______________________________________________<br>
seaside-dev mailing list<br>
<a href="mailto:seaside-dev@lists.squeakfoundation.org" target="_blank">seaside-dev@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev" target="_blank">http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev</a><br>
</div></div></blockquote></div><br></div>