You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: