-
Notifications
You must be signed in to change notification settings - Fork 24
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
testing: release 30.20190905.0 #12
Comments
kola tests pass:
|
Verified parent commit:
|
opened releng ticket for release: https://pagure.io/releng/issue/8756 |
PR open here: #13 |
ok everything is done except for:
This is pending an update from @jlebon and @lucab that will be coming on Monday. What this means is that people doing fresh installs will get the new media from the download page, but existing nodes won't upgrade until we do something on Monday. |
marking this as done since we finished everything up in #17 |
First, verify that you meet all the prerequisites
Pre-release
Promote testing-devel changes
From the checkout for
fedora-coreos-config
(replaceupstream
below withwhichever remote name tracks
coreos/
):git fetch upstream
git checkout testing
git reset --hard upstream/testing
/path/to/fedora-coreos-releng-automation/scripts/promote-config.sh testing-devel
git show
testing
branch on https://github.com/coreos/fedora-coreos-configBuild
testing
, and fill in version number using theN.YYYYMMDD.P
format, pending finalization of Version numbering for OS releases fedora-coreos-tracker#81)Sanity-check the build
Using the the build browser for the
testing
stream:testing
release (in the future, we'll want to integrate this check in the release job)Sign the CHECKSUMS file for releng
This is a stopgap until we do signing through fedora-messaging.
CHECKSUMS
file locally:CHECKSUMS
file you just downloaded matches the one from the pipeline Jenkins log outputgpg2 --output CHECKSUMS.sig --detach-sign CHECKSUMS
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.Signing artifacts and importing OSTree commit
In the future, the signing part will be integrated in the build job and the OSTree commit import will be integrated in the release job.
cosa run -d /path/to/previous.qcow2
) and verifying thatrpm-ostree upgrade
works andrpm-ostree status
shows a valid signature.Run the release job
testing
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 (instructions for starting a rollout TBD).
Update stream metadata
From a checkout of this repo:
The text was updated successfully, but these errors were encountered: