-
Notifications
You must be signed in to change notification settings - Fork 69
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
Extend image policy with numerical ordering #102
Labels
enhancement
New feature or request
Comments
I think this makes sense. I can take a stab at it, should be straightforward to implement. |
Would also be a nicer fit for using with |
29 tasks
relu
added a commit
that referenced
this issue
Feb 10, 2021
Converts the given list of tags to floats and compares them based on the ordering rule. If a tag is not convertable, it will err and fail to compute the latest version. Fixes #102 Signed-off-by: Aurel Canciu <aurelcanciu@gmail.com>
relu
added a commit
that referenced
this issue
Feb 11, 2021
Converts the given list of tags to floats and compares them based on the ordering rule. If a tag is not convertible, it will err and fail to compute the latest version. Fixes #102 Signed-off-by: Aurel Canciu <aurelcanciu@gmail.com>
relu
added a commit
that referenced
this issue
Feb 11, 2021
Converts the given list of tags to floats and compares them based on the ordering rule. If a tag is not convertible, it will err and fail to compute the latest version. Fixes #102 Signed-off-by: Aurel Canciu <aurelcanciu@gmail.com>
relu
added a commit
that referenced
this issue
Feb 11, 2021
Converts the given list of tags to floats and compares them based on the ordering rule. If a tag is not convertible, it will err and fail to compute the latest version. Fixes #102 Signed-off-by: Aurel Canciu <aurelcanciu@gmail.com>
relu
added a commit
that referenced
this issue
Feb 11, 2021
Converts the given list of tags to floats and compares them based on the ordering rule. If a tag is not convertible, it will err and fail to compute the latest version. Fixes #102 Signed-off-by: Aurel Canciu <aurelcanciu@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While alphabetical ordering works great with image tags that contain a RFC3339 timestamp, it's not suitable for CI build IDs, as these are numbers with no padding.
I propose we introduce a new ordering option called
numerical
to be able to correct detect the latest build for tags in the format<PREFIX>-<BUILD_ID>
.Example:
Given the tags
main-845d3a80-100
andmain-3e32dc8a-2
thenumerical
policy, unlikealphabetical
, will chosemain-3e32dc8a-100
as the latest build.The text was updated successfully, but these errors were encountered: