feat: configure CircleCI workflows

[mayurkale22]

Closes #50

[codecov-io]

Codecov Report

Merging #155 into master will increase coverage by 4.93%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #155      +/-   ##
==========================================
+ Coverage   93.84%   98.78%   +4.93%     
==========================================
  Files          41       41              
  Lines        3282     3282              
  Branches      385      385              
==========================================
+ Hits         3080     3242     +162     
+ Misses        202       40     -162

Impacted Files	Coverage Δ
...s/opentelemetry-core/test/trace/tracestate.test.ts	100% <0%> (+14.49%)	⬆️
.../opentelemetry-node-tracer/test/NodeTracer.test.ts	100% <0%> (+14.75%)	⬆️
...oks/test/asynchooks/AsyncHooksScopeManager.test.ts	100% <0%> (+15.9%)	⬆️
...pentelemetry-basic-tracer/test/BasicTracer.test.ts	100% <0%> (+17.28%)	⬆️
...etry-scope-base/test/noop/NoopScopeManager.test.ts	100% <0%> (+22.82%)	⬆️
packages/opentelemetry-basic-tracer/src/Span.ts	88.6% <0%> (+28.48%)	⬆️

[draffensperger]

For the node docker images that don't have browsers installed, we will need a separate test command (or environment variable) to disable the browser tests, since they run on yarn test, see

opentelemetry-js/packages/opentelemetry-core/package.json

Line 12 in 669b088

"test": "yarn test:node && yarn test:browser",

Maybe we need yarn test:node and yarn run test:browser and segment the tests in this file by that?

[mayurkale22]

I like the idea, made the appropriate changes in the config file. ptal

[draffensperger]

Sweet! Now the Node and browser tests can also run in parallel!

[bg451]

i know nothing about browser testing so going to defer on that front, but the rest looks good!

[mayurkale22]

c8 is supported on Node.js >= 10.12.0, looks like we need to fallback to nyc for code coverage. #93

Any thoughts?

[draffensperger]

Sweet! Now the Node and browser tests can also run in parallel!

[draffensperger]

Can we just disable coverage reporting for Node 8? I would assume the coverage would be the same as other Node versions (assuming no version-specific branching).

[rochdev]

c8 is supported on Node.js >= 10.12.0, looks like we need to fallback to nyc for code coverage.

I would say there are 2 options:

1. Switch to NYC to avoid having 2 tools. This means slower builds but would allow support for more Node versions.
2. As mentioned above, simply not running code coverage for Node 8. If there is any code specific to Node 8, it will appear as uncovered but that should be a very small portion of the codebase.

[mayurkale22]

I would say there are 2 options:

1. Switch to NYC to avoid having 2 tools. This means slower builds but would allow support for more Node versions.
2. As mentioned above, simply not running code coverage for Node 8. If there is any code specific to Node 8, it will appear as uncovered but that should be a very small portion of the codebase.

Tests and coverage are running with c8 tool, looks like falling back to nyc is right option for now.

[mayurkale22]

@markwolff FYI. For now, I have changed to nyc tool to support Node 8 build.