Travis CI: JWT addon will be deprecated

[azu]

JWT addon will be deprecated on April 17, 2018.
https://blog.travis-ci.com/2018-01-23-jwt-addon-is-deprecated

We need to look for an alternative.

Related

• JWT deprecation: Figure out how to test on Sauce labs during PR checks · Issue #13047 · ampproject/amphtml
• Travis JWT Addon will be discontinued on April 17, 2018 · Issue #133 · Level/memdown
• Look for an alternative to the JWT plugin for our Travis config · Issue #7798 · openlayers/openlayers
• JWT deprecation: Figure out how to test on Sauce labs during PR checks · Issue #13047 · ampproject/amphtml
• Use TravisCI JWT addon to encrypt Sauce Labs credentials · Issue #14789 · emberjs/ember.js

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[azu]

hls.js still use JWT addon.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[itsjamie]

This still needs to be fixed by April.

Options really seem to be:

• knowingly expose SauceLabs API credentials in environment variables (keep current state, PR builds for everyone)
• move SauceLabs API credentials to secure environment variables, only run SauceLab tests on repository collaborators
• build some tooling that doesn't output information into a log that is public, but will trigger SauceLabs, and shoot the result of the test back to the GitHub Checks API.

Does anyone know of a integration someone has built for SauceLabs that does this? The JWT addon has been going away for awhile.

[tjenkinson]

Not saying we shouldn't think about it, but the message said it was being removed last April not this April, so it's possible saucelabs changed their mind

[itsjamie]

Hah. The year did catch me. This is odd that it all still functions then.

Maybe we can let this go stale?

[tjenkinson]

I emailed them asking what their plan is On 14 Feb 2019, at 15:02, Jamie Stackhouse <notifications@github.com<mailto:notifications@github.com>> wrote: Hah. The year did catch me. This is odd that it all still functions then. Maybe we can let this go stale? — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#1572 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ADG-WRq1xXIlGhITVRf0Zf2FSBNe36Hoks5vNWxhgaJpZM4SKA8J>.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[michaelcunningham19]

I emailed them asking what their plan is

@tjenkinson Did you ever hear back?

[jonhoo]

For what it's worth, in fantoccini I just switched to using the browsers on Travis directly: jonhoo/fantoccini@06dccdd

[tjenkinson]

@michaelcunningham19 I never heard back from them

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.