FiloSottile
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.
ACK, I'll implement it ASAP! I think a simple "What branch to build" field on traviscron would do the trick, right?
Sure, that'd work. Maybe consider allowing multiple branches, too? I'd use it to test both the current dev branch and the last release.
Mutliple branches, multiple entries :) I'll make sure that it is supported
Filippo Valsorda
2013/11/25 Simon Weber [email protected]
Sure, that'd work. Maybe consider allowing multiple branches, too? I'd use it to test both the current dev branch and the last release.
— Reply to this email directly or view it on GitHubhttps://github.com/FiloSottile/travis-cron/issues/3#issuecomment-29249495 .