-
Notifications
You must be signed in to change notification settings - Fork 64
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 devfile library and odo version for registry tests #1367
Labels
Comments
openshift-ci
bot
added
area/ci
area/registry
Devfile registry for stacks and infrastructure
labels
Dec 1, 2023
blocking #998 |
This was referenced Dec 1, 2023
4 tasks
Putting back in review as we need to check how the odo version update will be handled |
1 task
I've created #1415 in order to investigate the usage of odo nightly builds in registry tests. As the new issue will take care of odo update, we can close the current issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Which area/kind this issue is related to?
/area ci
/area registry
Issue Description
As seen in the checks of this PR when someone tries to add multiple endpoints, from different components, sharing the same port the
validate_devfile_schemas
&check_odov3
tests are failing.For
validate_devfile_schemas
the reason is that we are using an old version of thedevfile library
for this test. In its latest version thelibrary
allows a devfile to have same ports for different component endpoints.For
check_odov3
we should wait until a new version is released, asodo
very recently updated theirlibrary
version. This way we should be able to pass thecheck_odov3
check having same ports for different component endpoints.Acceptance Criteria
library
version is updated insidetests/validate_devfile_schemas/go.mod
to a version that supports having same port numbers for different components.The text was updated successfully, but these errors were encountered: