opensource/podman
1
0
Fork 0
mirror of https://github.com/containers/podman.git synced 2025-05-20 16:47:39 +08:00
Code Issues Packages Projects Releases Wiki Activity

RELEASE_PROCESS.md: build artifacts locally

Browse Source 
The current PR process for release bump has the HEAD commit which bumps
version/version.go to the form `release+1-dev`. This makes Cirrus
publish release artifacts with `release+1-dev` and not `release`.

For example, the msi generated at https://cirrus-ci.com/task/5403901196238848
says podman-v4.0.3-dev.msi .

Building locally by checking out the released tag would generate the
correct artifacts and would also be faster and more convenient.

[NO NEW TESTS NEEDED]

Signed-off-by: Lokesh Mandvekar <lsm5@fedoraproject.org>
This commit is contained in:
Lokesh Mandvekar
2022-03-03 09:37:24 -05:00
parent ed59b89a43
commit a3497cee99
1 changed files with 14 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

26
RELEASE_PROCESS.md
View File

@ -236,18 +236,18 @@ spelled with complete minutiae.
1. Return to the Cirrus-CI Build page for the new release tag, confirm 1. Return to the Cirrus-CI Build page for the new release tag, confirm
(or wait for) it to complete, re-running any failed tasks as appropriate. (or wait for) it to complete, re-running any failed tasks as appropriate.
1. For anything other than an RC, download the new release artifacts from CI 1. For anything other than an RC, the release artifacts need to be published along
(the binaries which were actually tested). The items are with the release. These can be built locally using:
located under the *checks* tab in github for:
* `Cirrus CI / Alt Arch. Cross` - tarball for each architecture ```shell
* `Cirrus CI / OSX Cross` - two zip files (amd64 and arm64) $ git checkout vX.Y.Z
* `Cirrus CI / Windows Cross` - an `msi` file $ make podman-remote-release-darwin_amd64.zip podman-remote-release-darwin_arm64.zip podman-remote-release-windows_amd64.zip podman.msi podman-remote-static
$ mv podman-* bin/
$ cd bin/
$ tar -cvzf podman-remote-static.tar.gz podman-remote-static
$ sha256sum *.zip *.msi *.tar.gz > shasums
```
Under the "Artifacts" section of each task, click the "gosrc" link,
find and download the release archive (`zip`, `tar.gz` or `.msi`).
Save the the archive with a meaningful name, for example
`podman-v3.0.0.msi`.
1. The `podman-vX.Y.Z.dmg` file is produced manually by someone in 1. The `podman-vX.Y.Z.dmg` file is produced manually by someone in
possession of a developer signing key. possession of a developer signing key.
1. In the directory where you downloaded the archives, run 1. In the directory where you downloaded the archives, run
@ -263,8 +263,10 @@ spelled with complete minutiae.
that to upload the artifacts you previously downloaded, including that to upload the artifacts you previously downloaded, including
the `shasums` file. the `shasums` file.
* podman-remote-release-darwin.zip * podman-remote-release-darwin_amd64.zip
* podman-remote-release-windows.zip * podman-remote-release-darwin_arm64.zip
* podman-remote-release-windows_amd64.zip
* podman-vX.Y.Z.msi * podman-vX.Y.Z.msi
* podman-remote-static.tar.gz
* shasums * shasums
1. Save the release. 1. Save the release.