Hi all, I am following up on our discussion with Steve Hill and Rahul Somasunderam about publishing the Jenkins components to the Gradle Plugin Portal ( https://plugins.gradle.org/). As of now, this service assumes a single owner for the components, so any ownership transfers and release automation are complicated. This impacts the following components hosted on the Jenkins GitHub organization:
- Jenkins Templating Engine - https://github.com/jenkinsci/gradle-jte-plugin - Gradle JPI Plugin - https://github.com/jenkinsci/gradle-jpi-plugin - Gradle JPI2 Plugin - https://github.com/jenkinsci/gradle-jpi-plugin - Maybe?: Gradle Convention Plugin by Aarav Mahajan - https://github.com/aaravmahajanofficial/jenkins-gradle-convention-plugin (hosting request is coming soon) What we propose: - Create a new "jenkins" user on the Gradle Plugin Portal, transfer ownership of the components to it (for JTE, a separate confirmation is needed) - Jenkins Infra Team becomes an official owner of the user and hence can transfer permissions and upload credentials between maintainers, when needed - Ideally, the upload credentials could be provided only to the release environment - either in GitHub Actions or in a Jenkins instance. Keeping the release flow on GitHub Actions looks reasonable for now. Any feedback would be appreciated! Best regards, Oleg Nenashev -- 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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLB0QOtmO_SDRg61cjAc_oRA9RFAH%3DuEgWg-EjK7Ck37HQ%40mail.gmail.com.
