-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
More reliably determine CI Provider #1990
Comments
That package won't help with jenkins. It's more restrictive than our current check. |
The only way to figure this out is spin up a jenkins instance and go look at it. It's obviously not setting what it's documented to say it sets... https://wiki.jenkins.io/display/JENKINS/Building+a+software+project |
I set up a Jenkins Docker instance, ran
|
This is good. Can you please add Also can you setup a recorded run on the dashboard and make sure it works? |
Current behavior:
Some CI Providers show up as "unknown" with a suspected large amount of Jenkins CI runs going reported as "unknown"
Desired behavior:
@RandallKent mentioned this package may be helpful in determining the CI provider.
Update the current code to use package instead of env keys.
Link to current code: https://github.com/cypress-io/cypress/blob/issue-1942/packages/server/lib/util/ci_provider.coffee#L12
Versions
Cypress 3.0.1
The text was updated successfully, but these errors were encountered: