Ember.js - About. Rich internet application development using JavaScript, jQuery Mobile, and ColdFusion. Svenfuchs's gist: e4728d00bfd1d6559f4a. Travis CI still uses an Ember client that is based on an architectural mess which I have hacked together in last September or so and it is still using the old SC routing stuff and (a hacked version of) SC datastore. This is probably (part of) the reason why the current client behaves weird in some situations and entirely stalls in recent Chrome versions under heavy load.
I want to rebase/reimplement the client based on the current Ember routing stuff and architectural ideas, ideally preserving its functionality. At some point we separated assets out of the travis-ci web app (which mostly serves the JSON API, does authentication, etc) into a travis-assets repo which both ties into the web app (travis-ci) as a railtie for development AND is deployable to an asset host as a Sinatra app.
This setup uses a customized Rake::Pipeline and is watched/recompiled using Guard in development. I would ideally like to keep travis-assets separate from travis-ci but that's not a hard requirement.