<div dir="ltr"><font color="#330033"><font size="2"><font face="tahoma,sans-serif">Just looked at the Jenkins (previously Hudson) build server, and saw that there are separate tabs for Seaside 2.8 and Seaside 3.0.<br>Does this mean that we have separate builds for each one?<br>
<br>Avi.<br></font></font></font><br><div style="margin: 0pt;" name="sig_d41d8cd98f"></div><div class="gmail_quote">On Tue, Mar 8, 2011 at 10:03 PM, Dale Henrichs <span dir="ltr"><<a href="mailto:dhenrich@vmware.com">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 class="im">On 03/08/2011 10:42 AM, Lukas Renggli wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
You are already doing the #bleedingEdge builds, so that would only be useful<br>
from the perspective that Metacello will flush out dependency bugs that the<br>
current build process doesn't uncover. It would be nice if there were<br>
continuous development builds for all of the supported Pharo versions<br>
(whatever the list is) and adding Squeak builds would be nice, too.<br>
</blockquote>
<br>
It is the responsibility of the respective stakeholders to keep their<br>
ports up-to-date. Different Hudson/Jenkins instances can interoperate<br>
with each other, so we could combine the results of all build servers<br>
at a central location. However, I am not willing to maintain builds<br>
for platforms I don't care about.<br>
</blockquote>
<br></div>
That's fine...it _was_ worth mentioning though:)<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
The most useful from my perspective would be a #stable build. The stable<br>
build could be used to produce the Pharo release artifacts: image, changes,<br>
on-clicks based on the configurations...Right now there is potential for<br>
discrepancies between the configurations and the release artifacts....With a<br>
hudson build using the confg there'd be no discrepancies.<br>
</blockquote>
<br>
I think it would make sense to have a parallel "stable" Metacello<br>
based build that updates whenever the Metacello configuration changes.<br>
</blockquote>
<br></div>
That would be excellent!<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Pharo builds the stable Seaside release on Pharo1.2 only which AFIAK isn't<br>
supported by Seaside30 yet...<br>
</blockquote>
<br>
I don't think Pharo 1.2 stable is out yet, or did I miss something?<br>
</blockquote>
<br></div>
I was referring the the #stable version of Seaside30, not Pharo, sorry.<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
My Jenkins instance uses<br>
<a href="http://www.pharo-project.org/pharo-download/stable" target="_blank">http://www.pharo-project.org/pharo-download/stable</a> which still points<br>
to Pharo 1.1. As soon as this changes we will likely have to fix a few<br>
things.<br>
<br>
Also note that Pharo itself has several builds (that include Seaside)<br>
that are based on their development images:<br>
<a href="https://pharo-ic.lille.inria.fr/hudson/view/Pharo-Clients/" target="_blank">https://pharo-ic.lille.inria.fr/hudson/view/Pharo-Clients/</a><br>
</blockquote>
<br></div>
Right and those are all built against Pharo 1.2 and Seaside30 isn't supported on Pharo 1.2 yet ...<br><font color="#888888">
<br>
Dale</font><div><div></div><div class="h5"><br>
_______________________________________________<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>