Return of "Docker Cloud Build Status" parsing failure

[fmigneault]

Are you experiencing an issue with...

shields.io

🐞 Description

It was fixed a long while ago (#6235), but seems to have resurfaced recently.

Example: https://img.shields.io/docker/cloud/build/Ouranosinc/Magpie

🔗 Link to the badge

https://img.shields.io/docker/cloud/build/Ouranosinc/Magpie

💡 Possible Solution

No response

[github-actions[bot]]

Badge tested using npm run badge https://img.shields.io/docker/cloud/build/Ouranosinc/Magpie Output is available here

[PyvesB]

Hello @fmigneault 👋🏻

Thanks for reporting the issue! I think this is the same that I observed in #10241. We essentially need to get started on #9563. Any help would be welcome!

[fmigneault]

Hi @PyvesB. I have noticed this recent #10241 PR, and started getting failures around the same time. Is it directly caused by its changes (known cause why parsing fails)?

I'm all for unifying the Docker badges as proposed by #9563, but does that mean badges will stop working until this gets implemented? Is the integration planed in a near future? I'm worried about the current state since the issue has been open for over half a year without progress.

[PyvesB]

I have noticed this recent https://github.com/badges/shields/pull/10241 PR, and started getting failures around the same time. Is it directly caused by its changes (known cause why parsing fails)?

I suggest reading through #10241.

Is the integration planed in a near future? I'm worried about the current state since the issue has been open for over half a year without progress.

As said in my previous message, any help is welcome. Shields.io is an open-source project, many changes are driven by community contributions, with only one to two active maintainers who do their best at keeping things together with the limited time they can volunteer to this project. 😉