Skip to content
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

handle travis-pro (was: Coveralls throws a 500 error using gradle+jaCoCo) #4

Closed
dhalperi opened this issue Feb 12, 2014 · 3 comments · Fixed by #5
Closed

handle travis-pro (was: Coveralls throws a 500 error using gradle+jaCoCo) #4

dhalperi opened this issue Feb 12, 2014 · 3 comments · Fixed by #5

Comments

@dhalperi
Copy link
Contributor

See lemurheavy/coveralls-public#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!

@kt3k
Copy link
Owner

kt3k commented Feb 16, 2014

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.

@dhalperi
Copy link
Contributor Author

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:

  1. Change the service_name field to travis-pro from travis-ci.
  2. Add a field 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?

@kt3k
Copy link
Owner

kt3k commented Feb 19, 2014

Thanks for reporting in detail!

And I'm sorry for the inconvenience.

Any pull request is welcome! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants