Closed dhalperi closed 10 years ago
I have never used Travis Pro or Coveralls Pro and so I don't figure out the situation precisely.
But did you try --info
(or --debug
) option on gradle command (like gradle --info coveralls
)? This should show the entire JSON string sent to coveralls.io. This should help to isolate the cause of the problem.
Hi @kt3k ,
Following your advice I was able to extract the JSON string sent to coveralls.io, and then I was able to tweak it to work. Here's what I had to do:
service_name
field to travis-pro
from travis-ci
.repo_token
which maps to my repository's private token on coveralls.io.I wonder if we can add support for this to coveralls-gradle-plugin?
Thanks for reporting in detail!
And I'm sorry for the inconvenience.
Any pull request is welcome! :)
See https://github.com/lemurheavy/coveralls-public/issues/212
I wonder if you might have insight or have advice as to how I should debug this.
Note that I am using coveralls with a private repository and travis pro/coveralls pro. Have you tested this use case before?
Thanks!