-
Notifications
You must be signed in to change notification settings - Fork 94
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
Reporting CodeCoverage with Circle CI #11
Comments
adding detail debug output below, masking my api token
|
Hi @amitmawkin, I'm sorry you are getting that error. We found a bug some days ago, and we released a new version (1.0.4) that solves that problem. Unfortunately, JPM still hasn't fetch the new version. A temporary solution is to build from source: 1- Clone our repository https://github.com/codacy/codacy-coverage-reporter 2- run the command 3- in the project you want to send the coverage, instead of run with the
Please, let us know if this temporary fix worked for you. And we are going to pressure JPM to update to our latest release.
|
@amitmawkin I'll assume the temporary fix worked for you. Nevertheless we just worked with JPM and everything must be working. Closing the issue. |
If you click the link (https://jpm4j.org/#!/p/com.codacy/codacy-coverage-reporter) you'll see the version 1.0.4 is already available. If you remove it and uninstall it, you should have no errors. |
I am giving it up this time got the jar , still unsuccessful look at the version it still shows 1.0.0 ubuntu@box3130:~/lcd$ sudo java -jar codacy-coverage-reporter-1.0.4-assembly.jar --help -l | --language |
will try compiling from source, looks like jpm is all messed up |
please, ignore the printed version. It's a known bug that's already being fixed: #8 As you may see, if everything is well configured, you should have no problems running the coverage step: |
just installed codacy-coverage-reporter using jpm. Still get the error
using java 8 |
Hey @pjwalstrom can you provide us more details about your issue? everything should be fixed currently, it seems to be specific for your case. make sure you have the latest version:
if the error persists, provide us the information outputted by running with the debug flag ( |
I did jpm install today, but not sure which version it is. How can I figure that out? Still getting the error, though. Here is the info with --debug
|
Is the project public so we can look at it? It seems that you are not providing the correct path to the file, but it's hard to reproduce the error without any more information (like a concrete example) Have you look at our troubleshooting section? https://github.com/codacy/codacy-coverage-reporter#troubleshooting |
yes, I've looked at the troubleshooting, didn't help much. The file is there in the root directory
and I have the following config in my build.gradle, to be able to use jacoco
repo is not public, unfortunately |
|
can you confirm you are using the version 1.0.5 ? You can get the version through |
also, make sure the token you are using is updated: on Codacy platform, go to project settings, integrations, (add) Project API |
well, seems like it's version 1.0.0, but that does is not correct as far as I understand from the previous messages in this thread. The token is correct as according to the Project API Token
|
we released a new version yesterday (1.0.5) that fixes some bugs, and also fixes the print version. Try with the updated version. Instructions on how to remove installed version on https://github.com/codacy/codacy-coverage-reporter#build-from-source:
|
same problem with the new version
|
ok, I just realized we might be trying to send the file to api.codacy.com, whereas we are not on your hosted solution, but on amazonws... How would we go about to upload there? Didn't occur to me before that this could be a problem |
Hi, Sorry for this! In custom urls, you should use http://YOUR_URL:16006. If you curl to that port, you should get the component name back (api). |
As you can see in the code (we are going to improve the docs soon), you can set up a env variable to change the API url: |
Still having some issues, even if I curl (from https://api.codacy.com/swagger#!/commit/delta). We host codacy on our AWS, so we cannot use the Java library to upload the JSON. Note that even the GETs are returning a
Can anyone put some light? |
Hi, Please contact me at joao@codacy.com, as I will be checking on this today. Thanks, |
For those who are trying CURL as I did... the header for the API token is |
Bump codacy-api-scala
I am getting the following error when I am trying to report codacy code coverage feature language is java
The text was updated successfully, but these errors were encountered: