On 12 April 2013 16:05, Paul DeBruicker <pdebruic at gmail.com> wrote:
> Frank Shearar-3 wrote
>> We have a host of CI jobs running all in-image tests, loading various
>> packages into various Squeak versions and running same on various VMs.
>> We attempt to build the bleeding edge Interpreter and Cog VMs. We'd
>> like to do even more.
>>
>> All this requires machinery. We have build.squeak.org running jobs,
>> I've donated a FreeBSD slave and an OS X slave. We don't have any
>> Windows slaves, and we really need several more Linux build slaves to
>> take up the strain of the main jobs.
>>
>> Who would be willing to run builds on behalf of the community?
>>
>>
>> The fine print
>> --------------
>> As long as folk don't mind the potential security risks (Jenkins will
>> have the right to run arbitrary commands on the slave under its user
>> account), it's easy to set up.
>>
>> Easiest to set up are machines into which Jenkins can ssh: they just
>> require a user account and an SSH keypair. Machines running behind
>> NATs are also fine: I have a script prepared that will run the Jenkins
>> slave. (Of course that means that if you want to run the slave 24/7
>> you'd need to set up your own rc.d/system/init.d/whatever to keep the
>> process up.)
>>
>> Any takers?
>>
>> frank
>
>
> Hi Frank,
>
> It seems like you've done a lot of work to get this all running on Jenkins,
> and I know you've done a lot with the builderCI stuff.  Travis has recently
> added Mac OS X build slaves and are working to add Windows slaves.  Could
> some of what you've set up in Jenkins just be running on Travis-CI or do you
> need the build artifacts?

We definitely require some of the builds' artifacts: SqueakTrunk
produces a "minimal" 4.5 trunk while ReleaseSqueakTrunk produces
something that, with a passing grade from a human, could be published
to ftp.squeak.org.

But as it happens, we _do_ actually run some of build on Travis: if
you look at the bottom of https://github.com/frankshearar/squeak-ci
you'll see the build status. That's just `rake test`, which just
builds an interpreter VM and runs all the test suites in the image.
(But failing tests don't cause the build to go red, of course, which
is... less than truthful!)

At the moment the state of the art Travis-wise is to use FileTree and
builderCI for your package. The workflow around this isn't great, and
I hope to be able to contribute soon to making this smoother.

frank

> Thanks
>
> Paul