Announcement: ci.jenkins.io badges will be deactivated
See original GitHub issueUPDATE:
@MarkEWaite and @darinpope adopted the plugin, thus it doesn’t have to be removed from ci.jenkins.io, you’ll be able to continue using it.
As indicated in https://github.com/jenkins-infra/helpdesk/issues/3013
plugins.jenkins.io/embeddable-build-status is not actively maintained. The Jenkins security team had to address multiple vulnerabilities in jenkins.io/security/advisory/2022-06-22 to protect Jenkins project infrastructure. While the maintainer (thomas-dee) was happy to let us release the fixes we wrote, i.e. was responsive via email, he also told us he has no capacity to assist in any way. This is unsustainable. Consider removing the plugin from ci.jenkins.io.
We (the Jenkins Infrastructure team) will proceed to the removal of the embeddable-build-status plugin from https://ci.jenkins.io
As a result, all badges using this plugin with a markup containing https://ci.jenkins.io/buildStatus/
(builds from the public instance https://ci.jenkins.io) won’t work anymore.
An alternative has been proposed to put in place a self-hosted shield.io instance which would allow serving badges from ci.jenkins.io without this plugin.
Nothing change for badges retrieved from your own instance(s).
A pull request to indicate this deprecation/removal will be done on this repository, and other will be opened on the ~170 concerned repositories.
We invite you to follow the helpdesk issue for progress and/or comments.
Issue Analytics
- State:
- Created a year ago
- Comments:7 (5 by maintainers)
@hbazan-pp Here is a new twist! @MarkEWaite and @darinpope adopted the plugin, thus it doesn’t have to be removed from ci.jenkins.io, you’ll be able to continue using it.
@hbazan-pp another alternative I’ve added to the announcement is to put in place a self-hosted shield.io instance which would allow serving badges from ci.jenkins.io without this plugin.