-
Notifications
You must be signed in to change notification settings - Fork 242
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
update bundle check to consider release candidate versions to be valid #4409
Comments
@praveenkumar @anjannath We can modify the regex to allow additional characters in the version specification. But I'm not sure how to interpret the suffix - currently there is the |
@redbeam this is something different which is used as part of CI bits so we need to modify the regex to allow that also |
@praveenkumar But what about the suffix? What does |
and the separator between the bundle name and the custom suffix is currently a |
We can remove |
@anjannath Updating the job on snc side would be fine, but if there are any other places that could put their own suffix, maybe then we should change the regex. @praveenkumar I will submit a PR with this change. |
to allow more characters in bundle version field Issue #4409
from snc side crc-org/snc#982 is created to take care of |
to allow more characters in bundle version field Issue #4409
to allow more characters in bundle version field Issue #4409
to allow more characters in bundle version field Issue #4409
fixed in #4413 |
Currently the bundle check considers the following bundle name as invalid
crc_libvirt_4.18.0-ec.2_amd64.pr980.crcbundle
, it expects the version to be x.y.z without containing the-ec.2
part and the suffixpr980
should have the separator_
instead of a.
the CI on snc [0] is failing due to this strict checking, i think we can update the validation check to allow the version formats
x.y.z-rc.1
[0] https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/crc-org_snc/980/pull-ci-crc-org-snc-master-e2e-snc/1848580407633645568
The text was updated successfully, but these errors were encountered: