travis-ci/travis-core — pull request #144 by svenfuchs (2012-11-25 17:16:01+00:00)
Title: WIP [sf] rich states

apis that are affected by changing from result=[0|1] to state=[:passed|:failed|:errored|:canceled]

#### http apis

* v0: only used internally so we're free to change everything
* v1: can be kept stable so we don't break clients like bendywork's iphone app
* v2: is beta so we can change/add/remove fields as needed (affects state, result,
previous_state, previous_result, last_build_state, last_build_result)

#### pusher api

just gonna be changed according to our needs

#### status image api

how's this supposed to work? should we serve "errored" and "cancelled" images?
should we look for the last build that is either :passed or :failed on the given
branches?

#### github commit status task

can we just push custom status codes (i.e. add 'error', 'canceled' to 'success'
and 'failure')? can we use custom descriptions?

#### hipchat and flowdock tasks

how to adjust messages, colors etc to adapt to :error and :canceled statuses?

#### email

need to add images for new states:
* rename to passed-header-bg.png and failed-header-bg.png,
* add errored-header-bg.png and cancelled-header-bg.png

#### .travis.yml

what's with `on_[success|failure]` configuration in .travis.yml? do need to add
on_cancel and on_error?

`Event::Config.send_on?(type, event)` currently regards builds that have passed
as "success" and all other builds as "failure"