Unknown service could not get configuration

[ilanbiala]

/Users/Ilan/Development/hths-lunch/node_modules/codecov.io/lib/getConfiguration.js:19 throw new Error("unknown service. could not get configuration"); ^ Error: unknown service. could not get configuration at module.exports (project/node_modules/codecov.io/lib/getConfiguration.js:19:11) at sendToCodecov (project/node_modules/codecov.io/lib/sendToCodeCov.io.js:12:23) at Socket. (project/node_modules/codecov.io/bin/codecov.io.js:14:5) at Socket.emit (events.js:117:20) at _stream_readable.js:943:16 at process._tickCallback (node.js:419:13)

passing in 'mocha-lcov-reporter' to gulp-mocha.

Would also be nice to have better errors.

[cainus]

codecov.io needs a bunch of configuration data from your CI environment, like commit hash, branch name, build number, etc. This error comes up when it can't determine what CI service you're using.

Are you running from a CI service at all?

[ilanbiala]

No I was just running the tests and coverage locally.

[ilanbiala]

Is there a way to use this locally just whenever I run my tests to make sure a big feature is working?

[cainus]

I've never tested for that scenario. I'll try it this weekend, and see if I can get it working either way.

[cainus]

@stevepeak Hey! is there anyway to call the api without a build number/id? It doesn't make sense in the case of posting from your local machine. Does the api support that usecase? It seems like it doesn't... I tried buildId 'NONE' and got this back:

{"message": "Invalid value \'NONE\' (str): must match pattern ^\\\\d+(\\\\.\\\\d+)?$ (at build)", "uploaded": false}

Will I get away with it if I leave it off, or use all 0's?

Thanks!

[stevepeak]

You may set the value to null via this example: /v2?build=&commit=123123123... Thank you @cainus

[ilanbiala]

@stevepeak considering that all other codecov packages for other languages are under Codecov, shouldn't this one be there too? It would make it much easier to find and mean that Codecov is actually responsible for a rather large portion of the community.

[stevepeak]

@ilanbiala you being up a fine point. I'll have to chat to @cainus about this in more detail. Thank you

[ilanbiala]

I'm not saying @cainus shouldn't be a collab, but having Codecov in control means that it actually has to be actively developed by Codecov, but if someone else has the name, package, etc. Codecov feels little responsibility.

[cainus]

@stevepeak yeah... totally cool with me... All you have to do is fork... Did I give you npm publish rights?

[ilanbiala]

@stevepeak any progress on this?

[stevepeak]

Unfortunately I do not have to time to focus on this objective. I have a full time job outside Codecov and its my busy season. Thank you for understanding

[ghost]

:+1:

[stevepeak]

The only required variable are branch and commit the rest are optional. We must exclude the other arguments when uploading locally.

Working on this via #8

[stevepeak]

@ilanbiala @kytwb I will be deploying a new node uploader shortly. It will enhance Codecov to show off partial line coverage. Let me know if you are interested in helping out testing it. Thanks!

[ilanbiala]

@stevepeak sure you can ping me when it's ready for testing.

[ghost]

@stevepeak same :+1: