-
Notifications
You must be signed in to change notification settings - Fork 282
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
Support release iteration value for assemble workflow rpm #1921
Support release iteration value for assemble workflow rpm #1921
Conversation
Signed-off-by: Peter Zhu <zhujiaxi@dev-dsk-zhujiaxi-2a-5662414e.us-west-2.amazon.com> Signed-off-by: Peter Zhu <zhujiaxi@amazon.com>
Codecov Report
@@ Coverage Diff @@
## main #1921 +/- ##
============================================
+ Coverage 94.60% 95.00% +0.39%
Complexity 20 20
============================================
Files 178 44 -134
Lines 3633 220 -3413
Branches 27 27
============================================
- Hits 3437 209 -3228
+ Misses 192 7 -185
Partials 4 4 Continue to review full report at Codecov.
|
Hi @spotrh hope you can help us clear some confusions. Let' s say we build rpm for
If we release this directly as the 1st 1.3.0 release, would this be a problem after all? Thanks. |
dest="release_iteration", | ||
type=check_positive, | ||
default="1", | ||
help="The release/iteration number of deb/rpm packages, allow multiple revision of same package version (e.g. 2.0.0-1, 2.0.0-2, 2.0.0-3)" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
revision -> revisions
class AssembleArgs: | ||
manifest: IO | ||
keep: bool | ||
|
||
def __init__(self) -> None: | ||
|
||
def check_positive(value) -> int: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can add type for the input. value: str
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This does not allow me to block non-positive inputs.
The "Release" field is intended to be incremented when changes are made to the package that do not involve updating to a newer version of the software. When Version increments, you should reset Release (to prevent it from growing absurdly large) I'm not sure why you'd want to set Release to "123" as a starting value, but it's not harmful. |
I think I misunderstand some concept of my upgrade design. Thanks. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The fact that this is a new parameter that is only specific to deb/rpm, but is passed into a generic workflow is a red flag to me. Why do we need this at all? We don't vary build numbers for .tar.gz, so why are we trying to vary build numbers for deb?
- Upgrading between builds is not a supported scenario.
- We distinguish between builds by placing output in different build folders (with job number) via Jenkins, so why do we want to do this for rpm?
If you want to vary the build number, we should do it for all artifacts. Every build would generate a patch number based on, for example, date and time, e.g. 2.0.0.4071558 (April 7, 3:58).
class AssembleArgs: | ||
manifest: IO | ||
keep: bool | ||
|
||
def __init__(self) -> None: | ||
|
||
def check_positive(value) -> int: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Make this method private.
dest="release_iteration", | ||
type=check_positive, | ||
default="1", | ||
help="The release/iteration number of deb/rpm packages, allow multiple revision of same package version (e.g. 2.0.0-1, 2.0.0-2, 2.0.0-3)" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Help missing period, is too long and has grammar issues. Just say "Release number."
After some review I think this PR is not needed anymore. Thanks. |
Signed-off-by: Peter Zhu zhujiaxi@amazon.com
Description
Support release iteration value for assemble workflow rpm.
This PR add support for release/iteration value in rpm/deb packages.
It allows us to build packages with the same version without overriding existing packages.
It also allow users to upgrade the package to the same version but latest release/iteration.
It also allows us to assign the $BUILD_NUMBER to release/iteration in Jenkins so we can separate then when pushing to staging yum repo for testing.
Thanks.
Issues Resolved
#1545
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.