[Vm-dev] VM Maker: VMMaker.oscog-eem.662.mcz

[David T. Lewis]

On Thu, Apr 03, 2014 at 06:24:03PM -0700, gettimothy wrote:
>  
> Thanks Dave.
> 
> What is the path of code..starting from Eliot uploads an update to Cog or VMMaker.oscog.
> 
> Does it look like this: Eliot->source.squeak.org/VMMaker->Jenkins->SVN
> 

No, the two Jenkins jobs are not a part of the VM development process, and they
are not intended to produce VM source or executables for general distribution.
They are just an automated check for the current health of the sources, and a
check to make sure that someone who wants to build a VM can do so starting with
a clean Squeak image.

> Or is it something else?
> 
> More importantly, is there someplace where this is documented?
> 

As far as the Jenkins jobs, I suppose that you can think of the scripts as a
form of online documentation. I tried to make them as readable as I could,
and you can open them in a workspace and evaluate them step by step.

The script for the interpreter VM is:
  http://build.squeak.org/job/InterpreterVM/ws/VMUnixBuild.st 

The script for Cog is:
  http://build.squeak.org/job/CogVM/ws/VMCogUnixBuild.st

Dave


> thx
> 
> tty
> 
> 
> 
> ---- On Thu, 03 Apr 2014 17:11:51 -0700 David T. Lewis<lewis at mail.msen.com> wrote ---- 
> 
> 
>  
> On Thu, Apr 03, 2014 at 04:39:12PM -0700, gettimothy wrote: 
> > 
> > David, 
> > 
> > is http://build.squeak.org/job/CogVM/546/ a daily build based off the work Eliot is doing each time he uploads an update? 
> > 
> > How are the Jenkins build above and http://squeakvm.org/svn/squeak/branches/Cog/ related? 
> > 
>  
> The InterpreterVM and CogVM jobs that run on build.squeak.org are jobs that test 
> the overall process of loading VMMaker and various related packages needed for 
> generation of VM sources from Smalltalk source code (aka "slang"). The intent is 
> to verify that the source packages are loadable into a clean Squeak image, and 
> that they produce a coherent set of generated sources that can be used (along with 
> the platform sources that are managed in Subversion) to compile a working VM. 
>  
> It is necessary to run the compile step in order to ensure that the sources are 
> really in good shape. For example, the compile step recently detected a couple 
> of missing methods (the same ones that you had identified earlier by the way) 
> in the oscog VMMaker package. 
>  
> Assuming that the compile step is successful, the sources are assumed to be in good 
> shape, and the resulting source code is saved as the outcome of the Jenkins test. 
>  
> Dave 
>  
> 
>