On 6 December 2012 17:01, Frank Shearar <frank.shearar at gmail.com> wrote:
> On 6 December 2012 16:15, David T. Lewis <lewis at mail.msen.com> wrote:
>> On Thu, Dec 06, 2012 at 01:51:19PM +0000, Frank Shearar wrote:
>>> On 6 December 2012 13:24, David T. Lewis <lewis at mail.msen.com> wrote:
>>> >
>>> > 1) Save the final release image as image format 6504 prior to release.
>>> > This is done by resaving the image from an interpreter VM, which makes
>>> > it usable by a wider range of VMs including some very old interpreter VMs
>>> > that may still be in service (e.g. Edgars old Mac that does not have
>>> > an updated interpreter VM available).
>>>
>>> Given that our CI runs on RHell, with its attendant library problems,
>>> is it possible to use the InterpreterVM build's output in the
>>> SqueakTrunkOnInterpreter job?
>>>
>>> If so, we could adjust SqueakTrunkOnInterpreter's job/script slightly
>>> to do the above automatically, couldn't we?
>>>
>>
>> Yes, this can be easily added as a step in either the SqueakTrunk or
>> SqueakTrunkOnInterpreter job on box3. It's just a matter of running
>> the final image once more using the interpreter VM and a start script
>> consisting of "snapshot: true andExit: true".
>
> Right. The latest SqueakTrunk build _should_ do this, if you'd like to
> check it in about 8 minutes?

Well. It helps if I (a) use the right syntax for a conditional and (b)
don't bork the script. The script will now, hopefully,
* copy the base image into the target directory
* update the image
* open it with an interpreter VM and save it (to get the image format right)
* copy the updated image
* run the tests in the copy of the updated image
* produce the updated image as a build artifact

That will be build #49: http://squeakci.org/job/SqueakTrunk/49/.

frank

>> Dave
>>
>>