A release of the Apache mina API plugins (core and common) have exposed a cyclic dependency between the mina plugins, configuration as code, and other plugins. Details are into from https://issues.jenkins.io/browse/JENKINS-69034 <https://github.com/jenkins-infra/repository-permissions-updater/pull/2659> . A workaround is available, but a fix would be much better for users than the workaround.
The preferred fix needs a new release of the commons-lang3-api plugin <https://github.com/jenkinsci/commons-lang3-api-plugin/>. The current maintainer has not responded to previous requests nor to the current request <https://github.com/jenkins-infra/repository-permissions-updater/pull/2659> that asks to grant Tim Jacomb permission to maintain the plugin. The usual process would require a 2 week wait for the adoption request to "time out". I propose an exception in this case based on the need to deliver a new release of the commons-lang3-api-plugin. Tim is the Jenkins release officer, a long-standing contributor to the Jenkins project, and a strong contributor. I propose that Tim be granted permission immediately to maintain the commons-lang3-api plugin <https://github.com/jenkinsci/commons-lang3-api-plugin/> as requested in the RPU pull request <https://github.com/jenkins-infra/repository-permissions-updater/pull/2659>. Mark Waite -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/d7ca0365-4600-4097-8dd4-d3c9f93e5327n%40googlegroups.com.
