<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On 17 May 2016 at 01:03, Fabio Niephaus <span dir="ltr"><<a href="mailto:lists@fniephaus.com" target="_blank">lists@fniephaus.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi all,<div><br></div><div>I'm trying to understand how we build a new Squeak trunk image.</div><div>AFAIK, a Jenkins projects [1] runs squeak-ci [2] to build a new image, but I'm not sure I have</div><div>figured everything out that happens during the build process.</div><div>I guess squeak-ci opens an older Squeak image, updates it using the MCMcmUpdater and then</div><div>saves the new version. Or is there anything else that I am missing?</div><div><br></div></div></blockquote><div>That is the essential part of the process. The devil's in the details. If you look at <a href="https://github.com/squeak-smalltalk/squeak-ci/blob/master/update-image.st">https://github.com/squeak-smalltalk/squeak-ci/blob/master/update-image.st</a> you'll see the script squeak-ci uses to update the image. Most of that file is nonsense like doing sensible things when you're offline, or handling the vagaries of changed protocols in MCMcmUpdater and various other things. And dumping out enormous amounts of debugging information.</div><div><br></div><div>frank</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div></div><div>Best,</div><div>Fabio</div><div><br></div><div>[1] <a href="http://build.squeak.org/job/Trunk/" target="_blank">http://build.squeak.org/job/Trunk/</a></div><div>[2] <a href="https://github.com/squeak-smalltalk/squeak-ci" target="_blank">https://github.com/squeak-smalltalk/squeak-ci</a></div><div><br></div></div>
<br><br>
<br></blockquote></div><br></div></div>