-
Notifications
You must be signed in to change notification settings - Fork 116
Travis fails on all PRs #114
Comments
Does anyone at Google own this? |
I will look into this. |
By default, Travis tests fail on all external PRs due to security reason: https://docs.travis-ci.com/user/pull-requests/#pull-requests-and-security-restrictions There are ways to work around, e.g. https://blog.algolia.com/travis-encrypted-variables-external-contributions/ and discussion about it, e.g. OHDSI/Achilles#165 Since currently there's no plan to maintain this repository, I would only consider urgent CLs to merge in our codebase. Our suggestion is to migrate to our Golang library as Github is the source of truth for the repo and is actively maintained - https://github.com/google/go-containerregistry Thanks for your understanding. |
It looks like the Travis configuration uses secret environment variables to log into various docker repositories, but Travis only exports these variables on postsubmit runs (to prevent them from being stolen).
As a result, all PRs fail tests, which is not a great user experience.
The text was updated successfully, but these errors were encountered: