<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta content="text/html;charset=UTF-8" http-equiv="Content-Type"></head><body ><div style='font-size:10pt;font-family:Verdana,Arial,Helvetica,sans-serif;'>Thanks Dave.<br><br>What is the path of code..starting from Eliot uploads an update to Cog or VMMaker.oscog.<br><br>Does it look like this: Eliot->source.squeak.org/VMMaker->Jenkins->SVN<br><br>Or is it something else?<br><br>More importantly, is there someplace where this is documented?<br><br>thx<br><br>tty<br><br><br><div id="1"><br>---- On Thu, 03 Apr 2014 17:11:51 -0700 <b>David T. Lewis<lewis@mail.msen.com></b> wrote ---- <br></div><br><blockquote style="border-left: 1px solid #0000FF; padding-left: 6px; margin:0 0 0 5px"> <br>On Thu, Apr 03, 2014 at 04:39:12PM -0700, gettimothy wrote: <br>> <br>> David, <br>> <br>> is <a href="http://build.squeak.org/job/CogVM/546/" target="_blank">http://build.squeak.org/job/CogVM/546/</a> a daily build based off the work Eliot is doing each time he uploads an update? <br>> <br>> How are the Jenkins build above and <a href="http://squeakvm.org/svn/squeak/branches/Cog/" target="_blank">http://squeakvm.org/svn/squeak/branches/Cog/</a> related? <br>> <br> <br>The InterpreterVM and CogVM jobs that run on build.squeak.org are jobs that test <br>the overall process of loading VMMaker and various related packages needed for <br>generation of VM sources from Smalltalk source code (aka "slang"). The intent is <br>to verify that the source packages are loadable into a clean Squeak image, and <br>that they produce a coherent set of generated sources that can be used (along with <br>the platform sources that are managed in Subversion) to compile a working VM. <br> <br>It is necessary to run the compile step in order to ensure that the sources are <br>really in good shape. For example, the compile step recently detected a couple <br>of missing methods (the same ones that you had identified earlier by the way) <br>in the oscog VMMaker package. <br> <br>Assuming that the compile step is successful, the sources are assumed to be in good <br>shape, and the resulting source code is saved as the outcome of the Jenkins test. <br> <br>Dave <br> <br></blockquote><br></div></body></html>