Conversation
|
@davidread - hey David: any idea why this PR is not triggering at Travis CI? (https://travis-ci.org/github/ckan/ckanext-xloader/pull_requests). The "Update-Travis-Setup" branch triggered a Travis build but not the PR (nor an update to this PR) |
|
@kowh-ai The repo is enabled in Travis still 🤷 . I think it not showing up in the PR might be to do with the deprecation of the triggering from GitHub: https://docs.travis-ci.com/user/migrate/legacy-services-to-github-apps-migration-guide/ which would affect Travis for all repos in the CKAN GitHub org. However we've had builds attach to PRs two month ago, so I'm not sure why this is an issue on this latest PR. But it seems like a migration that should be done. There is a way to migrate them all at once here: https://travis-ci.com/organizations/ckan/repositories but I'll leave you to discuss that amongst the ckan tech team. |
take out the .encode() for py3
take out the .decode()
|
@davidread - thanks David - ended up being a problem with parsing my .travis.yml file (oops) - the Travis build is now green for all CKAN/Python releases 👍 |
|
Great work @kowh-ai ! |
3 participants
Update the Travis files to align with the other CKAN 2.9 Extensions