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

Support AppVeyor #429

Closed
giggio opened this issue Jan 13, 2015 · 8 comments
Closed

Support AppVeyor #429

giggio opened this issue Jan 13, 2015 · 8 comments

Comments

@giggio
Copy link

giggio commented Jan 13, 2015

AppVeyor is a very nice .NET/Windows CI Server:
http://www.appveyor.com/
And it already works with Coveralls. Here is an example build with AppVeyor, using Coveralls.NET:
Build:
https://ci.appveyor.com/project/code-cracker/code-cracker/build/1.0.0.303
Coveralls site:
https://coveralls.io/r/code-cracker/code-cracker
Source is here:
https://github.com/code-cracker/code-cracker/

I am not sure what is needed to have a supported CI server on Coveralls, but as it is already working, you might want to include it.

@barryokane
Copy link

+1 for this :)

@laedit
Copy link

laedit commented Jan 19, 2015

👍

1 similar comment
@ethanhann
Copy link

+1

@nickmerwin
Copy link
Member

Hi all, good call -- I've added http://www.nuget.org/packages/coveralls.io to our docs and listed AppVeyor to our supported CI's.

Thanks!

@giggio
Copy link
Author

giggio commented Feb 22, 2015

@nickmerwin Does this mean that Coveralls will be able to comment on PRs when the build happens in AppVeyor?

@nickmerwin
Copy link
Member

@giggio it's possible, but I'm not sure that integration library supports it, although it would be trivial to add.

From Appveyor's docs (http://www.appveyor.com/docs/build-configuration):

APPVEYOR_PULL_REQUEST_NUMBER

Our API docs (https://coveralls.zendesk.com/hc/en-us/articles/201350799-API-Reference) show how to associate a build with a PR using this post parameter:

service_pull_request

@jayvdb
Copy link

jayvdb commented Jun 10, 2015

Multi-job builds do not appear to group reports together.

@stevenvachon
Copy link

I had to add an env variable to make it work: #888 (comment)

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

No branches or pull requests

7 participants