-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
stable: new release on 2023-12-04 (39.20231119.3.0) #826
Comments
@prestist (cc. @yasminvalim) do you mind if I take over the release process next week? |
@c4rt0 Yes that would be amazing |
Re-run: |
Ahh https://jenkins-fedora-coreos-pipeline.apps.ocp.fedoraproject.org/blue/organizations/jenkins/build-arch/detail/build-arch/3130/pipeline failed because of coreos/coreos-assembler#3669 coreos/fedora-coreos-config#2745 isn't backported to the |
Since all the tests except the |
First, verify that you meet all the prerequisites
Edit the issue title to include today's date. Once the pipeline spits out the new version ID, you can append it to the title e.g.
(31.20191117.3.0)
.Pre-release
Promote testing changes to stable
ok-to-promote
label to the issuestable
branch on https://github.com/coreos/fedora-coreos-configManual alternative
Sometimes you need to run the process manually like if you need to add an extra commit to change something in
manifest.yaml
. The steps for this are:git fetch upstream
git checkout stable
git reset --hard upstream/stable
/path/to/fedora-coreos-releng-automation/scripts/promote-config.sh testing
stable
branch on https://github.com/coreos/fedora-coreos-configBuild
stable
, leave all other defaults). This will automatically run multi-arch builds.Sanity-check the build
Using the the build browser for the
stable
stream:stable
release (in the future, we'll want to integrate this check in the release job)IMPORTANT: this is the point of no return here. Once the OSTree commit is
imported into the unified repo, any machine that manually runs
rpm-ostree upgrade
will have the new update.Run the release job
stable
and the new version IDAt this point, Cincinnati will see the new release on its next refresh and create a corresponding node in the graph without edges pointing to it yet.
Refresh metadata (stream and updates)
Rollout general guidelines
When setting a rollout start time ask "when would be the best time to react to
any errors or regressions from updates?". Commonly we select 2PM UTC so that the
rollout's start at 10am EST(±1 for daylight savings), but these can be fluid and
adjust after talking with the fedora-coreos IRC. Note, this is impacted by the
day of the week and holidays.
The later in the week the release gets held up due to unforeseen issues the more
likely the rollout time allocation will need to shrink or the release will need
to be deferred.
Manual alternative
fedora-coreos-stream-generator
binary is up-to-date.From a checkout of this repo:
sync-stream-metadata
job syncs the contents to S3Update graph manual check
NOTE: In the future, most of these steps will be automated.
Housekeeping
The text was updated successfully, but these errors were encountered: