Support Coveralls notification to Github
Hello there,
Coveralls.io is able to comment on Github PRs, for example, when
the coverage has decreased, or fell bellow a certain
percentage.
Usually we hide our project's coveralls api key on an encrypted
variable.
And PRs can't use these variables.
Because of that, we can't tell coveralls that a PR has happened,
and it can't comment on the PR.
How can we solve that? Maybe a specific variable can be used only
on some context?
The discussion also happened here:
https://github.com/jdeering/coveralls.net/issues/12#issuecomment-75...
And here:
https://github.com/lemurheavy/coveralls-public/issues/429#issuecomm...
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Feodor Fitsner on 24 Feb, 2015 02:42 AM
I see. How is that API key is used? Maybe we could do built-in integration with coveralls. Is there any guide/sample how to integrate with it?
2 Posted by giggio on 24 Feb, 2015 04:39 AM
Very simply. If you follow Coveralls.net code: https://github.com/jdeering/coveralls.net
You will see it is simply some REST endpoint.
API reference is here: https://coveralls.zendesk.com/hc/en-us/articles/201350799-API-Refer...
Support Staff 3 Posted by Feodor Fitsner on 26 Feb, 2015 07:11 PM
I've replied here: https://github.com/jdeering/coveralls.net/issues/12#issuecomment-76...
Still not sure if we should pull this to the UI - maybe do that in appveyor.yml only.
4 Posted by giggio on 26 Feb, 2015 08:53 PM
Appveyor.yml only is fine for me, that is what I use.
Maybe you could wait for adoption, if it happens then you work on the UI.
5 Posted by jayvdb on 09 Jun, 2015 11:24 AM
Also looking for coveralls integration of some sort.
6 Posted by jayvdb on 10 Jun, 2015 11:06 AM
Eventually found enough information in https://github.com/lemurheavy/coveralls-ruby/blob/master/lib/coveralls/configuration.rb#L68 , which talks about parts of the API not documented at https://coveralls.zendesk.com/hc/en-us/articles/201350799-API-Reference (e.g. Appveyor support uses service_number , service_branch and service_build_url) , so that I could add python support, however ..
then I found that coveralls doesnt group builds by git hash (or anything else) - so multi job builds are not supported.
Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:56 AM.