Skip to content
A set of scripts to build Pharo images with Hudson
Smalltalk Shell
Find file
Pull request Compare This branch is 269 commits ahead, 31 commits behind renggli:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
builds
cache
images
mcz
oneclick
scripts
sources
templates
tests
.gitignore
.travis.yml
LICENSE
README.md
build.sh
buildImageErrorCheck.sh
buildTravisStatusCheck.sh
build_clone.sh
build_env_vars
build_image.sh

README.md

Intro

Serge got things started using Lukas' builder, with travis-ci, so I'm aiming to team up Metacello and builder to make the setup and maintenance of CI test scripts for Pharo and Squeak as painless as possible ...

Using builderCI

  1. Read Travis CI docs
  2. Create your own .travis.yml file by copying the template travis.yml into the home directory of your git project.
  3. Decide which platforms you want tested (Squeak-4.3, Squeak-4.4, Pharo-1.3, Pharo-1.4 and/or Pharo-2.0) and edit the .travis.yml file to create your build matrix. If you are using Metacello with your project you shouldn't have to make any other edits. Metacello and FileTree are pre-installed in the image.
  4. Create a tests/travisCI.st that contains the code to load your project, its tests and launch the test harness.
  5. Enjoy.

Dealing with Failure

Here's a the output for a build that failed because of unit test failures. Scroll to the bottom of the console list and you'll see the following:

***********************************************
    Results for builderCI Test Suite
3 run, 1 passes, 0 expected failures, 1 failures, 1 errors, 0 unexpected passes
***********************************************
*** FAILURES *******************
    SampleTest debug: #testFailure.
*** ERRORS *******************
    SampleTest debug: #testError.
***********************************************

Tests that fail or produce error are listed. You should be able to copy the the expressions and evaluate them in a workspace:

SampleTest debug: #testError.

Debugging Travis CI scripts

At the beginning of the run, everything written to the Transcript is routed to to the TravisTranscript.txt file. You can list the contents of the file by including the following line in your .travis.yml file:

   - cat TravisTranscript.txt

or conditionally dump the TravisTranscript.txt file upon an error or test failure:

   - $BUILDER_CI_HOME/buildImageErrorCheck.sh
   - $BUILDER_CI_HOME/buildTravisStatusCheck.sh

Projects using TravisCi and builderCI

Travis CI results

Build Status

Something went wrong with that request. Please try again.