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

Registry testing should skip deprecated stacks #1586

Closed
michael-valdron opened this issue Jun 4, 2024 · 1 comment
Closed

Registry testing should skip deprecated stacks #1586

michael-valdron opened this issue Jun 4, 2024 · 1 comment
Labels
area/registry Devfile registry for stacks and infrastructure

Comments

@michael-valdron
Copy link
Member

Which area is this feature related to?

/area registry

Which functionality do you think we should add?

Why is this needed? Is your feature request related to a problem?

If the devfile registry testing skips stacks and stack versions that are deprecated, the current failures experienced in main branch testing would be resolved.

Detailed description:

As stacks or stack versions become deprecated it is not required to test against those entries, therefore it would be ideal that the automation only tests against stacks and stack versions that are not labelled as deprecated.

Describe the solution you'd like

To archive this, we can alter get_stacks.sh to filter out stack and stack version entries that are labelled as deprecated.

Optionally, we can also choose to only do this if TEST_DELTA is false or unset to still test against any changes to the deprecated entries, though I don't feel this is necessarily an important criteria for this solution.

Describe alternatives you've considered

Every time there is test failures due to these scenarios we can manually add the stack entry to skip. This however would increase the maintenance on the community devfile registry service we would need to do.

Additional context

@openshift-ci openshift-ci bot added the area/registry Devfile registry for stacks and infrastructure label Jun 4, 2024
@Jdubrick
Copy link
Contributor

Deprecated stacks should still be tested to ensure they are working

@michael-valdron michael-valdron closed this as not planned Won't fix, can't repro, duplicate, stale Jun 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/registry Devfile registry for stacks and infrastructure
Projects
Status: Done ✅
Development

No branches or pull requests

2 participants