[Jenkins-infra] Jenkins Core Release Automation Status

Olblak me at olblak.com
Mon Jun 17 09:37:17 UTC 2019


Hi Everybody,


I am organizing a feedback session on Jenkins core release automation this Friday at 3PM (UTC+2).
meet.google.com/kqn-kioe-uns 

This session will focus on how Jenkins is configured on top of k8s and used to trigger a new release and where that release artifacts are published.

If you want to experiment by yourself before the session, they are two endpoints deployed at the moment:

* https://release.ci.jenkins.io
* https://release.repo.jenkins.io

Those two services are running on an AKS cluster, fully automated and reachable from the jenkins infrastructure vpn so feel free to request your access on jenkins-infra/openvpn <https://github.com/jenkins-infra/openvpn>, you'll also need to be in the right ldap group, so feel free to ping me mentionning your jenkins account. 

Remark: Currently, releases done via release.ci.jenkins.io are not 'official' and use a fork repository called 'olblak/jenkins' instead of jenkinsci/jenkins.

Next steps are:
* Clarify who can/should request a new signing certificate.
* Clarify who can/should create a new gpg key.
* Ensure that the process is well protected.
* Define a clear process for the community to contribute Jenkins core packaging (Debian,Redhat,etc.)
* Identify artifacts promotion process from staging to production.

Ps: I created a gitter <https://gitter.im/jenkinsci/release> channel (yet another channel) if you have any questions on this topics, feel free to ask them there.

Best,

Olblak
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-infra/attachments/20190617/3856bbc9/attachment.html>


More information about the Jenkins-infra mailing list