-
Notifications
You must be signed in to change notification settings - Fork 65
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
Badge images displaying status unknown when they are known #1525
Comments
URLs for this project like https://ci.appveyor.com/api/projects/status/avsuce1irt8h63u2/branch/master?svg=true render the badge as I would expect, but I'd rather use the |
Interestingly the other project in this account seems to work.
|
There are two projects in AppVeyor with |
https://ci.appveyor.com/project/erickt/serde was created back in Sep 2015 and never built. |
Thanks! I reached out to erickt. Is there any way to prevent our badge from being intentionally or unintentionally DOS'ed by someone duplicating the project, other than using the badge at the |
You can't prevent someone from creating a duplicate project. Yes, you are always welcome to submit a ticket to sort it our in case of any issues. |
Wait, so if someone forks a project and then enables appveyor on their fork, will the original repo have this problem? |
Nope, as forked repo will have a different |
So how did erickt/serde end up with the same name as serde-rs/serde? https://github.com/erickt/serde/ |
I think erickt/serde at some point got transferred to serde-rs/serde and then erickt forked it from serde-rs/serde back to erickt/serde. |
He could be a owner/collaborator in that repo or, alternatively, he could edit repository name on project settings in AppVeyor. |
I'm not sure why this is allowed, if appveyor's access to github is managed through github oauth? |
Everyone can setup a new project building any public repository. Obviously, they won't be able to setup webhook for that project or put commit statuses as they don't have "write" rights, but anyone can "read" public repos. |
Ok, it's just unfortunate that this affects the official project's badge :( |
That's why badge ID should be used. |
It's another annoyance to have to look up that badge ID.... other services that have badges don't have this problem.... |
Also perhaps owner/repo badges should be entirely disabled then, if they're not guaranteed to work? |
The Appveyor badge shows "failing" even though the build is passing. According to appveyor/ci#1525 they are completely broken.
Hi, not sure if this is related to #1288 or #1468, but I'm currently seeing "build: unknown" badges when I expect the build to be known :-/
Example page attempting to display a badge: https://crates.io/crates/serde
HTML for the badge, currently displaying the
badge: unknown
image for https://ci.appveyor.com/api/projects/status/github/serde-rs/serde?svg=true&branch=master:Project in Appveyor showing a successful build currently: https://ci.appveyor.com/project/serde-rs/serde, more specifically, the last build on the master branch succeeded: https://ci.appveyor.com/project/serde-rs/serde/build/1.0.229
Am I doing something wrong?
rust-lang/crates.io#693
The text was updated successfully, but these errors were encountered: