suzanne.soy/travis-web
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
The Ember web client for Travis CI
1,130 Commits 34 Branches 291 Tags 56 MiB
PostScript 85.7%
JavaScript 6.5%
Handlebars 2.7%
Sass 2.4%
CSS 1.9%
Other 0.8%
c7561ee13e
Go to file
Piotr Sarnacki c7561ee13e Properly display matrix keys when build does not have all keys 
When additional items are included into matrix via 'matrix.include' key
in .travis.yml they may contain config keys, which are not available on
build.

For example build can contain only 'rvm' key, but we may add the
following include:

    matrix:
      include:
        - rvm: '2.0.0'
          env: 'FOO=bar'

In such case, we need to take into account also keys from additional
job, not only from the build.

(closes #172)
2013-04-06 01:48:32 +02:00
.localeapp Run rake localeapp:update 2013-03-12 14:02:48 +01:00
assets Properly display matrix keys when build does not have all keys 2013-04-06 01:48:32 +02:00
config switch to puma, make app reload in development mode 2012-10-17 16:19:42 +02:00
lib Fix passing alt=default param 2013-03-05 21:08:14 +01:00
locales Merge branch 'master' into 142-ShowPrTitle 2013-03-18 09:43:29 +11:00
play update log.js and adapt styles for fold name tags 2013-02-27 22:39:10 +01:00
public Run specs on sauce labs 2013-03-27 20:08:28 +01:00
script Rename TEST_SUITEs to ruby, phantomjs and saucelabs 2013-03-28 11:43:49 +01:00
spec Fix passing alt=default param 2013-03-05 21:08:14 +01:00
.buildpacks Change buildpacks 2012-10-30 02:20:58 +01:00
.gitignore Add locales.js to .gitignore 2012-12-17 22:23:32 +01:00
.rspec Add some color to rspec 2012-11-10 15:47:33 +01:00
.slugignore Don't ignore assets directory when building slug 2012-10-30 02:23:06 +01:00
.travis.yml need to return true after testing for TEST_SUITE 2013-03-29 20:29:43 +01:00
Assetfile disable production compilation for now 2013-02-27 22:51:13 +01:00
config.ru simplify app creation and rename "custom_branch" to "alt" 2013-02-25 17:42:03 +01:00
CONTRIBUTING.md Added missing word "repo" 2013-03-18 23:05:06 -03:00
Gemfile Merge branch 'master' into ps-ember-update 2013-03-09 12:48:35 +01:00
Gemfile.lock update the Gemfile to use the secure rubygems, and remove the common queue from the sidebar 2013-03-10 00:07:20 +13:00
Guardfile make assetfile reusable 2012-10-03 16:34:21 +02:00
Guardfile.phantom add a guardfile for running specs 2012-07-05 00:47:05 +02:00
LICENCSE mit license 2012-10-03 13:38:40 +02:00
NOTES.txt Remove getPath/setPath from NOTES, it's already fixed 2012-08-12 13:42:43 +02:00
Procfile Revert "Fix procfile to rerun app when lib/**/* changes" 2013-02-21 22:22:22 +01:00
Rakefile Extracted localeapp-handlebars_i18n to gem 2012-12-04 00:17:58 +09:00
README.md Add build badge 2013-03-19 01:05:04 -03:00
run_jasmine.coffee Run specs on sauce labs 2013-03-27 20:08:28 +01:00
run_mocha.js try using jasmine for specs 2012-06-25 23:58:27 +02:00
seeds.sql add seeds gitignore config/travis.yml 2012-07-21 20:03:29 +02:00
travis-web.gemspec rename gemspec 2012-10-03 15:24:47 +02:00

README.md

Travis CI ember web client

Build Status

Running the app

In order to run the app you need to install dependencies with:

bundle install

Then you have to run the server, the easiest way to do this is to use foreman:

bundle exec foreman start

Now you can open localhost:5000

By default it uses official API at https://api.travis-ci.org, but you can set your own enpoint using:

API_ENDPOINT="http://localhost:300/" bundle exec foreman start

This will run against API run locally.

Compiling assets manually

bundle exec rakep
ENV=production bundle exec rakep

Running the spec suite

First, start the app (see above).

bundle exec foreman start

To run the Ruby specs, run rspec against the spec/ directory:

bundle exec rspec spec/

To run the Jasmine specs, open the spec page: localhost:5000/spec.html

i18n

Localization for travis-web is managed via localeapp. If you are interested in improving the existing localizations or adding a new locale, please contact us on irc (#travis) and we will set you up.

Please do not edit the YAML files directly.

Localization data can be synced with the following rake task:

bundle exec localeapp:update

This will publish any new keys in en.yml, as well as any missing keys from your handlebars templates and pull down the latest localizations.

note: You will need to have the localeapp api key exported to LOCALEAPP_API_KEY