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
Env Var COVERALLS_SERVICE_JOB_NUMBER maps to wrong config variable #303
Comments
Kind-of related to #300 |
I'm basing this on the descirptions of the ENV Vars documented in the node-coveralls library: https://github.com/nickmerwin/node-coveralls |
Found the related issue here:
That matches up with my description in the initial comment. |
Fixes the mapping between default (eg. `COVERALLS_*`) env vars and the equivalent config values, which had some mismatches for job identification cases. Fixes #303
@ashleysommer thanks for the detailed issue! Definitely looks like we've made a mistake here and set some incorrect values; I've opened a PR (#314) with the fixes you've recommended -- if you could give it a glance over to make sure I've caught all your comments, that'd be much appreciated! |
Fixes the mapping between default (eg. `COVERALLS_*`) env vars and the equivalent config values, which had some mismatches for job identification cases. Fixes #303
Fixes the mapping between default (eg. `COVERALLS_*`) env vars and the equivalent config values, which had some mismatches for job identification cases. Fixes TheKevJames#303
SERVICE_JOB_NUMBER and SERVICE_NUMBER are different things.
build #1938
step #2
"pytest with coverage"
The CI-specific config handlers get the job_id right, but the code that processes environment vars seems to get it a bit confused, and doesn't provide a way to set SERVICE_JOB_ID.
coveralls-python/coveralls/api.py
Lines 198 to 200 in 5799354
Should be:
The text was updated successfully, but these errors were encountered: