Skip to content

Commit

Permalink
Changing how coverage is initialized
Browse files Browse the repository at this point in the history
  • Loading branch information
MichaelGHSeg committed Nov 14, 2024
1 parent 3a2ba14 commit 24d4645
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 1 deletion.
1 change: 1 addition & 0 deletions .buildkite/pipeline.yml
Original file line number Diff line number Diff line change
@@ -1,4 +1,5 @@
env:
COVERAGE: true
SEGMENT_CONTEXTS: 'snyk,npm,aws-credentials,ecr,npm-publish'
SEGMENT_BUILDKITE_IMAGE: 'analytics-next-ci-agent'
steps:
Expand Down
2 changes: 1 addition & 1 deletion packages/config/src/jest/config.js
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ const createJestTSConfig = (
* No need to manually run yarn build all the time.
* This resolve packages for ts-jest so typescript compilation happens in-memory.
*/
...(process.env.CI === 'true'
...(process.env.COVERAGE === 'true'
? {
collectCoverage: true,
coverageReporters: ['json'],
Expand Down

0 comments on commit 24d4645

Please sign in to comment.