Skip to content

Add support for polling Travis CI builds by SHA #12

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 7, 2016

Conversation

phillipj
Copy link
Member

@phillipj phillipj commented Apr 6, 2016

Compared to the nodejs.org repo, Travis doesn't pick up newly created PR's from nodejs/readable-stream. Strangely enough it does pick up commits and builds them though.

Therefore these changes adds support for polling Travis builds by commit SHAs rather than PR #id alone. The bot tries to do a smart choice about which polling to use by checking if Travis has had any builds triggered by PR's lately, if not if starts to poll by SHA.

Disclaimer for sore eyes: this introduces a lot of duplicated code between polling PR's and SHAs. I'd rather get this up-n-running and clean up the mess later.

Refs nodejs/readable-stream#194 (comment)

@phillipj phillipj mentioned this pull request Apr 7, 2016
@phillipj phillipj force-pushed the poll-travis-by-sha branch from 8a4b30a to 5856c8a Compare April 7, 2016 19:13
Compared to the nodejs.org repo, Travis doesn't pick up newly created PR's
from nodejs/readable-stream. Strangely enough it does pick up commits and
builds them though.

Therefore these changes adds support for polling Travis builds by commit SHAs
rather than PR #id alone. The bot tries to do a smart choice about which polling
to use by checking if Travis has had *any* builds triggered by PR's lately,
if not if starts to poll by SHA.
@phillipj phillipj force-pushed the poll-travis-by-sha branch from 5856c8a to cf21a4f Compare April 7, 2016 19:17
@phillipj phillipj merged commit 8824234 into master Apr 7, 2016
@phillipj phillipj deleted the poll-travis-by-sha branch April 7, 2016 19:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant