Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Tests: support for travis jwt ends on april 17th #9508
We're currently using JWT for our tests in saucelabs. This was needed, because we do not want to expose credentials inside PR builds. Sadly there seem to be some concerns with it, so travis decided to shut it down.
Loosing JWT also shuts down our saucelabs tests, so we've to act somehow. I had no time to think/work on an alternative way of authenticating. Ideas are welcome.
What about this approach:
The service should keep a blacklist of files (i.e. .travis.*) when a travis build must not be triggered.
I know that this involves an additional service, but it's a realtive simple one. We already have the travis ci config, just the handling of secure env variables can be disabled, because we can control when to expose them.