-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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 request: From AppVeyor build artifact #555
Comments
I don't know exactly how AppVeyor's API allows to fetch artifacts, but that is definitely an interesting use-case. A difficult aspect of this is to convey how it works to others from the main page. |
Thanks for reviewing, @espadrine. And I appreciate that your model is so simple that each use generally needs just a one line description. That's fantastic. If you're agreeable to this design, can you tell us what timeline it might be implemented in, or whether you'd entertain a pull request that adds the functionality? |
@AArnott It would take me at least a few months to get to implementing this, as most of the time I have dedicated to shields.io is spent on sysadmin, maintaining existing APIs that weather down or hit unexpected limits, and reviewing PRs. I would absolutely entertain a PR that adds the functionality. It may need work in try.html to have an explanation in the dialog box. |
Thanks, @espadrine. |
The Endpoint badge #2838 provides a building block for this. |
I'd like to display badges based on the contents of an AppVeyor build's artifact files. The build would drop special text files which AppVeyor would report as artifacts. These text files would contain just one line of text:
<SUBJECT>-<STATUS>-<COLOR>
The artifact filenames would follow some agreed upon convention such as
SOMENAME.shield
.The shield could then be displayed via a URL like this:
https://img.shields.io/appveyor/ci-artifact/USERNAME/PROJECT/SOMENAME.svg
See dotnet/pinvoke#24 for a full description of what we want to create.
The text was updated successfully, but these errors were encountered: