I should have been more precise. I think the infrastructure team should discuss the impact of Microsoft's stopping maintenance of those plugins.
We've been willing to discuss a possible migration from the Jenkins wiki because we're concerned about the effort to maintain it. We maintain the Jenkins wiki with very little administrative effort, yet are concerned enough about risk from administration that we included it as a discussion topic and assigned me to create a migration plan. If we're willing to discuss the administration risk of the Jenkins wiki, I think we owe it to ourselves to discuss the
ci.jenkins.io risk from the loss of Azure plugin maintainers. If the infrastructure team decides that Microsoft end of maintenance for those plugins in 2024 is not an issue, that's a fair choice, but I think it needs to be discussed.
We needed 12 months to move
the Jenkins Jira server to a new provider from the start of discussions to completion of the migration. A service as crucial as
ci.jenkins.io will need longer than that. Feb 2024 is 36 months away. I think we should start the discussions.
I'll start a discussion thread in the Jenkins infra mailing list.
Mark Waite