On Fri, Apr 24, 2020 at 9:12 AM Olblak <m...@olblak.com> wrote: > Hi, > > While we agreed to switch weekly versions to the new release environment, > we didn't clarify who should be responsible for those weekly releases and > when we trigger them. > As long as the process is not 100% stabilized I think it makes sense for > me to trigger them on Monday morning UTC and then when 100% confident we > can use cronjob for it but I think we'll still need someone responsible for > them. > > Any thoughts? > > I think we should have you run the release Monday morning UTC while we're stabilizing and we should continue that pattern even after we switch to a scheduled job to do the build.
I think you're proposing a "build master" role for the weekly build. That role would investigate build failures, raise issues, and monitor their resolution. I like that idea. It might fit as a role that could be taken by one of many people, overseen by the Release Officer. I'd be willing to take that role, but we'd need to shift the release time to UTC midday rather than UTC morning so that I would not need to be watching a build in the middle of my night. Would you be willing to consider the idea of a DataDog dashboard or a Jenkins job which shows the overall health of the weekly build? That dashboard or Jenkins job would show the results from: - Weekly build release job - Weekly build package job - Install latest Debian package <https://ci.jenkins.io/job/Infra/job/acceptance-tests/job/install-latest-debian-package/> job - Install latest Red Hat package <https://ci.jenkins.io/job/Infra/job/acceptance-tests/job/install-latest-redhat-rpm/> job - Install latest OpenSUSE package job (future) - Install latest Windows package job (future) The test results aggregator plugin <https://plugins.jenkins.io/test-results-aggregator/> might help us combine test results from multiple jobs into a single summary job. > > -- > 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/1aa27bc3-a3ff-4f3c-bf71-d13e260dbe80%40www.fastmail.com > . > -- 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/CAO49JtHW2rJikBWOhfzsoUb2r%2BehJ6ZQPa0EV1oEbEw46Qa3Sw%40mail.gmail.com.
