<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Sat, Dec 14, 2013 at 5:13 PM, Frank Shearar <span dir="ltr"><<a href="mailto:frank.shearar@gmail.com" target="_blank">frank.shearar@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 14 December 2013 20:53, Chris Muller <<a href="mailto:asqueaker@gmail.com">asqueaker@gmail.com</a>> wrote:<br>
> Hi Frank! I actually put this message out to lure you into this discussion.<br>
> :) Because, I want to move on 4.5 and I knew you had _something_ out there,<br>
> but couldn't remember all the details.<br>
<br>
</div>You used the right kind of bait, that's for sure :)<br>
<div class="im"><br>
> The issues I faced with needing to get a new image were:<br>
><br>
> - I had to research the mailing list to find out where to download it. An<br>
> automated build server is great for doing continuous *testing* and<br>
> reporting, but it seems like for end-user downloads we should have a copy<br>
> available at the usual place (<a href="http://ftp.squeak.org" target="_blank">ftp.squeak.org</a>).<br>
> - When I downloaded the image from CI, updated, and ran the tests, I found<br>
> there were more tests failing than in another image that was simply updated<br>
> from 4.4. Something seemed to be wrong with the image state.<br>
> - Since I was not really certain what all was done in that image, I could<br>
> not trust putting it on the <a href="http://squeak.org" target="_blank">squeak.org</a> FTP site. The only way I could be<br>
> SURE enough about the state of an image put there was to take the archive<br>
> release image (4.4) and simply update it myself and save it.<br>
><br>
> So, the overarching requirements:<br>
><br>
> - Downloadable from <a href="http://squeak.org" target="_blank">squeak.org</a> domains.<br>
> - A way to know exactly how it was built: This means knowing which prior<br>
> _full release image_ was started with, and what changes (both code and<br>
> objects) were made.<br>
> - Reproducible build. My idea since 4.2 was to have a utility method on<br>
> ReleaseBuilder do all of this so it would be visible straight in the trunk<br>
> repository. I guess I always thought of the CI's responsibility as a<br>
> on-going "test-status reporting" mechanism more than a deployment tool.<br>
<br>
</div>Yep, yep, yep. I agree with all the above.<br>
<br>
There is something wrong with the base image state at the moment,<br>
partly because I'm incapable of pulling out ToolBuilder-Tests in less<br>
than at least three attempts (sigh!). (*)<br>
<br>
So the idea I've always had with CI was this:<br>
* take a known-good base image (not happening right now :( )<br>
* update it<br>
* run a battery of tests on a copy of the image<br>
* run the release process on the image (ReleaseSqueakTrunk) </blockquote><div><br></div><div>Perfect. (I assume you meant ReleaseBuilder).</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Every now and then, someone can take the latest ReleaseSqueakTrunk<br>
artifact, takes a look at the test results on <a href="http://build.squeak.org" target="_blank">build.squeak.org</a>, plays<br>
around with it. If it's fit for purpose, he or she pushes the artifact<br>
up to <a href="http://ftp.squeak.org" target="_blank">ftp.squeak.org</a> as a release candidate. Everyone else bangs on<br>
it, and if the release manager's happy, it ships.<br>
<br>
I do think that manual verification is important, because we don't<br>
want random broken builds on <a href="http://ftp.squeak.org" target="_blank">ftp.squeak.org</a>, even if they're declared<br>
as alpha quality.<br></blockquote><div><br></div><div>Absolutely.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Additionally, as you rightly point out we need someone to advertise<br>
<a href="http://build.squeak.org" target="_blank">build.squeak.org</a>. Not just that it's there and we use it, but how to<br>
get a bleeding-edge image, for instance.<br></blockquote><div><br></div><div>A link from the main web-site and also from an appropriate page(s) in the wiki would be a start. We should have a page on the wiki dedicated to explaining the CI server overview anyway.</div>
<div><br></div></div></div></div>