filosottile/travis-cron

This web app allows you to trigger Travis CI builds periodically

The Travis CI cron trigger

This project permits to have Travis CI builds triggered periodically, for example to test scrapers.

At Travis they will eventually implement cron (ref: travis-ci/travis-ci#582), meanwhile, I hope this helps :)

Technically

This project is made of two parts:

• A Django web app (running at http://traviscron.pythonanywhere.com) that lets users add new triggers to the queue.
• A Python module, travis_ping, that given a GH project name and a Travis OAuth token, triggers a rebuild.

The actual work is done by a continuously running process, crontab-like: python manage.py runworker.

Probably the first 3rd party app made using the new Travis API!

travis-cron's Issues

getting unhandled exception when trying to register new job

i tried to register my job (klrmn/pytest-rerunfailures)...the first time it sent me thru asking for github credentials, which i okayed. and then got an 'unhandled exception' page. i waited a week to see if it had crashed after the important parts, but there was no sign of a run triggered by the service.

so i tried registering it again. i got 'unhandled exception' immediately, with the url http://traviscron.pythonanywhere.com/callback?code=8c9eae2ce5a242c2d145&state=67990841a07b23ea414db0b3a39282

chrome on OSX.
let me know if you need more info.

/requests is deprecated

travis-ci/travis-web#255

http://docs.travis-ci.com/api/#builds

▶ oiim/scraper

Hi,

Recently, I've registered a project on http://traviscron.pythonanywhere.com/ which is oiim/scraper

Actually it is ◼ disabled. Is it possible ▶ it ?

Thank you

Builds seem to rerun last, not run branches

It looks like the build that's getting triggered is the last build to have run. Most of the time this is exactly what I want, but it's not always.

Take a look at https://travis-ci.org/simon-weber/Unofficial-Google-Music-API/builds and https://travis-ci.org/simon-weber/Unofficial-Google-Music-API. The build that's getting cronned corresponds to a PR, which is useless in my case because of secure params.

It would be nice if you instead parsed the travis config (eg https://github.com/simon-weber/Unofficial-Google-Music-API/blob/develop/.travis.yml) and ran the requested branches.

Please fix static urls for https support

Everyone can trigger https://nosnch.in/c8651ba4a3

How to rely on monitoring that everyone can cheat? Please, change it and make hidden in https://travis-ci.org/FiloSottile/travis-cron/settings.

Sorry for ruining your expectations about an interesting issue.

Builds not running?

https://travis-ci.org/simon-weber/Unofficial-Google-Music-API/builds

I checked a few of the other builds and it didn't seem that they were, either.