Skip to content
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

RELEASE_PROCESS.md: build artifacts locally #13416

Merged

Conversation

lsm5
Copy link
Member

@lsm5 lsm5 commented Mar 3, 2022

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.

Signed-off-by: Lokesh Mandvekar [email protected]

@mheon @ashley-cui @TomSweeneyRedHat @rhatdan @baude PTAL

/cc @containers/podman-maintainers

DO NOT MERGE without LGTMs from @mheon and @ashley-cui

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 3, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lsm5

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 3, 2022
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 <[email protected]>
@lsm5 lsm5 force-pushed the release-artifacts-process branch from 85ca86d to a3497ce Compare March 3, 2022 15:08
@lsm5 lsm5 requested review from mheon and ashley-cui March 3, 2022 15:09
@rhatdan
Copy link
Member

rhatdan commented Mar 3, 2022

LGTM
@mheon @cevich @baude PTAL
@containers/podman-maintainers PTAL

Copy link
Member

@ashley-cui ashley-cui left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@cevich
Copy link
Member

cevich commented Mar 3, 2022

@rhatdan you should do [CI:DOCS] in the PR title for these, no need to wait for all those CI jobs 😀

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 3, 2022
@openshift-merge-robot openshift-merge-robot merged commit 5fc8c9b into containers:main Mar 3, 2022
@lsm5
Copy link
Member Author

lsm5 commented Mar 3, 2022

umm, I'd have preferred to wait for @mheon 's review, but I guess we can revise it once he gets back. No biggie.

@lsm5 lsm5 deleted the release-artifacts-process branch March 3, 2022 19:54
lsm5 added a commit to lsm5/podman that referenced this pull request Mar 7, 2022
Follow up to pr#13416

Insert line breaks to get rid of the horizontal scroll bar.

Resolves: containers#13416 (comment)

Co-authored-by: Ashley Cui <[email protected]>
Signed-off-by: Lokesh Mandvekar <[email protected]>
tricktron pushed a commit to tricktron/podman that referenced this pull request Mar 14, 2022
Follow up to pr#13416

Insert line breaks to get rid of the horizontal scroll bar.

Resolves: containers#13416 (comment)

Co-authored-by: Ashley Cui <[email protected]>
Signed-off-by: Lokesh Mandvekar <[email protected]>
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 21, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants