Hello, I am happy to share that I received a code signing certificate for the Jenkins project, so the next step is to update the release environment with the right code signing certificate and the right gpg key, verify that they are in a safe location (both on Azure Key vault) and then finalize the publishing part.
Quick reminder on the current state of this project. I deployed a specific Jenkins instance in the vpn, it's called release.ci.jenkins.io. This instance is configured with two jobs one to trigger release and a second one to trigger packaging for a specific release for debian,redhat,suse, msi release.ci.jenkins.io configuration is defined on jenkins-infra/charts <https://github.com/jenkins-infra/charts/blob/master/helmfile.d/jenkins-release.yaml>. I created a new repository named "github.com/jenkins-infra/release", where that repository contains scripts, Jenkinsfiles and pod template definition used by release.ci.jenkins.io Finally, I reused and adapted scripts from jenkinsci/packaging, with the last PR located here, <https://github.com/jenkinsci/packaging/pull/130> I wish I had the time to refactor more those scripts to reduce the dependency on pkg.jenkins.io but I'll probably have to take some shortcut. Today people that I consider who should be able to trigger a job from release.ci.jenkins.io are olblak, danielbeck, olivergondza, oleg_nenashev, anybody else will have read-only access from the vpn. Feel free to ask if you have any questions, or just suggestions. Cheers -- 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 on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/0e4fac96-0039-487d-a267-f6e7df04cdc9%40www.fastmail.com.
