Hi, I want to publish a new release of the gradle-jpi-plugin. Previous release artifacts of that plugin have been signed with some GPG key, e.g. http://repo.jenkins-ci.org/public/org/jenkins-ci/tools/gradle-jpi-plugin/0.5.0/
Signing artifacts seems to be a good idea in general. Is there some kind of policy for that? Shall I use my own key or is there a special Jenkins key? Daniel -- 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]. For more options, visit https://groups.google.com/d/optout.
