Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Check for env.CONTINUOUS_INTEGRATION

See original GitHub issue

instead of just process.env.CI.

Issue Analytics

State:
Created 6 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

kevvacommented, May 25, 2017

Only one I found was Shippable. Although all of them supports CI AFAIK which makes this kinda moot.

0reactions

Qix-commented, May 25, 2017

Agreed. CI should be sufficient.

Thanks for the report 😃

Top Results From Across the Web

What is a CI/CD Environment? - PagerDuty

The CI in CI/CD stands for Continuous Integration. CI is an automation process within development that continuously builds, tests, and merges new code...

Detect CI via environment variable

Detect CI via environment variable to enable custom test logic.

cucumber/ci-environment - GitHub

This library detects the CI environment based on environment variables defined by CI servers. If a CI server is detected, a CiEnvironment struct...

6 best practices for integration testing with continuous ...

Run integration tests until something fails · Determine what needs to be added or modified · Drill down into unit testing · Go...

Continuous Integration and Test Environment Challenges

But a CI pipeline is only part of the solution. The other critical part is the test environment used for test execution.