After some discussion with the people involved in the process, I'll start at 11AM UTC instead of 3PM UTC, so we have more time to fix any unplanned issues.
On Wed, Apr 15, 2020, at 9:51 AM, Oleg Nenashev wrote: > I confirm my availability for tomorrow. Will also spend some time today to > merge changes into the Jenkins core so that the release includes some real > enhancements and fixes for Jenkins users. > > Regarding the schedule, it would be great to start the release process a bit > earlier so that we have more time to fix issues if any. E.g. we could start > the release Pipeline early so that artifacts are ready to packaging when US > wakes up. > > Best regards, > Oleg > > > > On Tuesday, April 14, 2020 at 9:04:03 PM UTC+2, Olblak wrote: >> Today, during the infra meeting, we discussed creating a new weekly release >> from the new process this Thursday the 16th at 3PM UTC. >> While there won't be major features, the purpose of this release is to >> validate that everything is working as expected in a real scenario. >> >> >> I am proposing the following agenda >> >> >> * 3PM(UTC), I start the release job and we release directly to the master >> branch and directly on repo.jenkins-ci.org/releases. >> Currently the release job take approximatively 1h30 >> >> >> * 4:30PM(UTC), or early if ready, I start the packaging process in order to >> publish artifacts to pkg.jenkins.io >> Currently, the packaging job take approximatively 15min to run and I >> estimate the script sync.sh to take 15min to run >> >> * 5PM(UTC), we verify that the release is working correctly. >> >> During the whole all process we'll be on IRC, #jenkins-infra channel >> >> Again feel free to raise any concerns you may have. >> >> Cheers >> >> On Tue, Apr 14, 2020, at 4:44 PM, Oleg Nenashev wrote: >>> Thanks a lot to Olivier and all other contributors who invested lots of >>> time to get it done! I am looking forward to finally get it over the line, >>> at least for weeklies. >>> >>> FWIW, the Sunday's weekly got delayed (due to Easter). We could make an >>> attempt to cut this release using the new flow without waiting for the next >>> weekly. >>> >>> Best regards, >>> Oleg >>> >>> >>> On Tue, Apr 14, 2020 at 4:32 PM Olblak <[email protected]> wrote: >>>> __ >>>> Hi Everybody, >>>> >>>> This project is getting to the end and I am looking for a last round of >>>> reviewers and testers before planning a weekly release with the new >>>> process. >>>> I opened a pull request (link >>>> <https://github.com/jenkins-infra/release/pull/53/files>) with >>>> instructions about how to trigger a release but currently, it only covers >>>> weekly releases. >>>> Our first objective is to successfully release weekly versions from >>>> https://release.ci.jenkins.io, then we'll focus on stable and security >>>> releases. >>>> >>>> For security releases, the way I see it: >>>> 1) We add two security profile, one for weekly and the second one for the >>>> stable in order to trigger a release from jenkinsci-cert/jenkins:master to >>>> https://repo.jenkins-ci.org/releases/ >>>> 2) Trigger packaging job(weekly or stable profile), >>>> 3) We manually merge from jenkinsci-cert/jenkins:master to >>>> jenkinsci/jenkins:master >>>> >>>> For stable releases: >>>> 1) We update the stable >>>> <https://github.com/jenkins-infra/release/blob/master/profile.d/stable> >>>> profile branch to 'stable-<version>', variable JENKINS_GIT_BRANCH) >>>> 2) We trigger stable release job >>>> 3) We trigger stable packaging job >>>> >>>> Another topic that needs clarification is who should be able to trigger a >>>> release from release.ci.jenkins.io and who will trigger the different >>>> releases? >>>> >>>> Cheers >>>> >>>> -- >>>> You received this message because you are subscribed to the Google Groups >>>> "Jenkins Infrastructure" group. >>>> To unsubscribe from this group and stop receiving emails from it, send an >>>> email to [email protected]. >>>> To view this discussion on the web, visit >>>> https://groups.google.com/d/msgid/jenkins-infra/8656f659-17ef-49f3-b265-950488fd9b45%40www.fastmail.com >>>> >>>> <https://groups.google.com/d/msgid/jenkins-infra/8656f659-17ef-49f3-b265-950488fd9b45%40www.fastmail.com?utm_medium=email&utm_source=footer>. >>> >>> -- >>> 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]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLBfFoN7FYM-gFO8NXixcz6nduoLH_HP6ysEsdRrPEgQcA%40mail.gmail.com >>> >>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLBfFoN7FYM-gFO8NXixcz6nduoLH_HP6ysEsdRrPEgQcA%40mail.gmail.com?utm_medium=email&utm_source=footer>. >> > > -- > 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]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/cb175d2d-b8f3-403c-a0d1-5c2ebfdbfea6%40googlegroups.com > > <https://groups.google.com/d/msgid/jenkinsci-dev/cb175d2d-b8f3-403c-a0d1-5c2ebfdbfea6%40googlegroups.com?utm_medium=email&utm_source=footer>. -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/460c46ba-3205-4748-a90e-f52e1da5f36b%40www.fastmail.com.
