chore(ci): remove more old connection security stuffs

[johnjbarton]

No description provided.

[AppVeyorBot]

✅ Build karma 2559 completed (commit 0ff176f937 by @johnjbarton)

[karmarunnerbot]

✅ Build karma 161 completed (commit 0ff176f937 by @johnjbarton)

[karmarunnerbot]

✅ Build karma 160 completed (commit 0ff176f937 by @johnjbarton)

[devoto13]

@johnjbarton Nice! Let's see if this solves SauceLabs error on master.

[devoto13]

@johnjbarton I had a PR to update the check in integration-tests repo: https://github.com/karma-runner/integration-tests/pull/11/files. But I think now it is better to use something similar to what you do in https://github.com/karma-runner/karma/pull/3461/files. Will update the PR soon.

[devoto13]

@johnjbarton After some digging it seems that the problem is this line. My theory is that https://github.com/karma-runner/integration-tests/tree/master/saucelabs test tries to start Sauce Connect proxy, but fails because it is already started by Travis itself. Can't check it though, because SAUCE_* variables are only available to the master branch and I can't access them in my debugging branch.

[johnjbarton]

I think the integration-tests are installed in the karma-runner/karma travis session so I don't think that .travis.yml is read. But your theory about the sauce connect could still be right, I just added that line as a guess. I "unguessed" and I updated the integration_tests travis file also, thanks.

[karmarunnerbot]

🎉 This PR is included in version 5.0.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀