-
-
Notifications
You must be signed in to change notification settings - Fork 548
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
Make AppVeyor check PRs (was: Please add CI build badges to the README) #330
Comments
@sschuberth Build badges have always been there as long as I recall in the README. See May be they should be instead at the top of the readme? |
Doh, sorry for that. I was so used from other projects to see these at the top that I simply did not scroll further down. Feel free to close this unchanged, or to move them to the top of the README as you prefer. But on a related note, I don't see Appveyor builds being enabled for PRs. Is that something you could enable? |
OK, so let's move these to the top. |
Well, looking at e.g. #321 and clicking on "Show all checks" I would have expect to see AppVeyor in there, but I only see TravisCI ... |
Agreed, I would have loved to see this there too. But the problem is that Appveyor does not offer a "Github integration" but instead only a webhook. Hence the builds do not show up in a GH PR check. I will not complain: this is a free service but unfortunately as with many things in MSFT-centric development environments, the appveyor config is often arcane and circumvoluted |
As a side note, #321 may need some work and in particular the base url to link to a lincense may need be moved to a config option/config files. As it may also breaks some other features that require Jinja (for custom HTML templates, even though this feature may go away). |
Thank you to @sschuberth for reporting this Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>
That's not correct :-) I recently helped to enable AppVeyor CI checks for PRs for the Git LFS project, see e.g. git-lfs/git-lfs#1574.
At least it's on their list: appveyor/ci#88. |
hum, I cannot see a way to enable an Appveyor integration though. |
ATM the way appveyor is configured is with a plain webhook added to the GH repo and setup to receive push and pr events |
Not sure what went wrong for you. I usually go to https://ci.appveyor.com/projects/new, select the "GitHub" tab, and add the project I want to have built. That makes PRs for me build out of the box. |
OK, let me try to delete the integrations and webhook and recreate that from scratch |
I deleted and recreated the Appveyor projects and it looks like this fixed the problem. |
* based on @crwood https://github.com/gridsync/gridsync irc-notify.py * GPL-licensed * also updated the appveyor config to send IRC notifications Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>
And added a script forked from @crwood for IRC notifications. This covers appveyor/ci#88 nicely |
And you can see the first build working here: https://ci.appveyor.com/project/nexB/scancode-toolkit/build/1 |
@sschuberth as you can in #334 we now both IRC notification and PR properly showing Appveyor as a check. |
Could we please get build badges as part of the README, for both TravisCI and AppVeyor, and each for the
master
anddevelop
branches? That helps to quickly see the health status, and to access the latest build artifacts for testing.The text was updated successfully, but these errors were encountered: