Skip to content

miguelfrde/travieso

Repository files navigation

travieso

Build Status

Contents

  1. About
  2. Deploy
  3. Contributing

About

Travieso allows to see Travis CI build jobs directly on Github to quickly see exactly which part of the build failed.

travieso

Deploy

General instructions

In your .travis.yml file add the following lines (just use your own url):

notifications:
  webhooks:
    urls:
      - https://travieso.example.com/notifications
    on_success: always  # default
    on_failure: always  # default
    on_start: always    # default is never

Besides that make sure you do the following:

  • The Travis CI token you use when configuring the app ($TRAVIS_TOKEN) is the Travis CI token for the user that was used to setup the repository. You can find this toke in the user's profile page. You can change it in your repo settings: https://github.com/[Your account]/[Your repo]/settings/hooks/[Travis CI hook service ID]. More information.

  • The GitHub token that you use should have the repo:status scope enabled. Click here to generate this token for your GitHub account.

  • Don't forget to add an environment variable TASK=job_name to each of your matrix tasks. This is the environment variable that travieso reads to set the commit status context.

Refer to our .travis.yml for an example.

Heroku

Click the button below to deploy directly to Heroku. You'll need the tokens mentioned before ready and in the webhook notifications section of your .travis.yml, use the url: https://[app name].herokuapp.com/notifications.

Deploy

Google App Engine

Coming soon...

Kubernetes

Coming soon...

Manually

In the server where you want to run the app, run the following:

$ git clone https://github.com/wizeline/travieso
$ export GITHUB_TOKEN="Your github token"
$ export TRAVIS_TOKEN="Your travis token"
$ ./travieso/bin/web

Contributing

See CONTRIBUTING.md

About

Travis CI build job status directly on GitHub!

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 3

  •  
  •  
  •