using travisCI for github-based Metacello work

Following Serge's lead[1], I've setup travisCI for my Metacello work.

You can see the current latest build/test status here[2].

I've forked Lukas' builder project[3], with an eye toward stripping it down and aiming it towards travisCI ... summary of test results instead of catting files, plus failing the build on test failure, right now the build fails when there is a catastrophe:)

Dale

[1] http://forum.world.st/Using-github-amp-Travis-CI-for-a-Smalltalk-project-tt4633864.html
[2] http://travis-ci.org/#!/dalehenrich/metacello-work
[3] https://github.com/dalehenrich/builder

renamed the builder fork to builderCI[1] ...

[1]https://github.com/dalehenrich/builderCI

----- Original Message -----
| From: "Dale Henrichs" <[hidden email]>
| To: [hidden email]
| Cc: "Serge Stinckwich" <[hidden email]>
| Sent: Friday, June 8, 2012 8:41:34 PM
| Subject: [Metacello] using travisCI for github-based Metacello work
|
| Following Serge's lead[1], I've setup travisCI for my Metacello work.
|
| You can see the current latest build/test status here[2].
|
| I've forked Lukas' builder project[3], with an eye toward stripping
| it down and aiming it towards travisCI ... summary of test results
| instead of catting files, plus failing the build on test failure,
| right now the build fails when there is a catastrophe:)
|
| Dale
|
| [1]
| http://forum.world.st/Using-github-amp-Travis-CI-for-a-Smalltalk-project-tt4633864.html
| [2] http://travis-ci.org/#!/dalehenrich/metacello-work
| [3] https://github.com/dalehenrich/builder
|

Dale Henrichs wrote

I've forked Lukas' builder project[3]

I've been working on an all-Smalltalk solution, where Jenkins just delegates everything (or as much as you want) back to an image. This way, there is no shell scripting, and you can live debug your build scripts, like we're used to. I've been using it quite successfully on my local Jenkins server, and plan on releasing it soon, and soon as I polish it up and slap a GUI on it...

Sean

Very cool... I look forward to seeing it ... I've stripped the scripts down to a bare minimum so I would really like to see what you've done for driving the process from the image

Unlike Jenkins, TravisCI doesn't produce any build artifacts (permanent) just fires off a "build" on push/pull/branch/commit to a github project runs a series of scripts and fails the build when a script item fails with non-zero exit status ... output is standard out on console ...

Not very sophisticated, but I like the idea of running unit tests on every commit rather than have to run the full suite before a commit .... knowing that particular errors showed up at a particular commit is nice since you can come back later and fix any problems on a branch from the commit ....

Presumably the "build" can push build artifacts to permanent storage somewhere else on the internet ...

I also plan to preload fileTree and Metacello so the scripting api can be used to for loading ....

Fun times!

Dale

----- Original Message -----
| From: "Sean P. DeNigris" <[hidden email]>
| To: [hidden email]
| Sent: Friday, June 8, 2012 8:47:54 PM
| Subject: [Metacello] Re: using travisCI for github-based Metacello work
|
|
| Dale Henrichs wrote
| >
| > I've forked Lukas' builder project[3]
|
| I've been working on an all-Smalltalk solution, where Jenkins just
| delegates
| everything (or as much as you want) back to an image. This way, there
| is no
| shell scripting, and you can live debug your build scripts, like
| we're used
| to. I've been using it quite successfully on my local Jenkins server,
| and
| plan on releasing it soon, and soon as I polish it up and slap a GUI
| on
| it...
|
| Sean
|
| --
| View this message in context:
| http://forum.world.st/using-travisCI-for-github-based-Metacello-work-tp4633976p4633979.html
| Sent from the Metacello mailing list archive at Nabble.com.
|