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

Add registry probing timeout environment variable to the acceptance test template #1095

Closed
michael-valdron opened this issue Apr 4, 2023 · 1 comment · Fixed by devfile/registry#175
Assignees
Labels
area/ci area/registry Devfile registry for stacks and infrastructure

Comments

@michael-valdron
Copy link
Member

michael-valdron commented Apr 4, 2023

Which area/kind this issue is related to?

/area ci
/area registry

Issue Description

In #1086, optional registry probing was added to the integration test suite to delay testing in case of concurrent deployment of the target registry. This was done as a requirement to issues which occurred during staging deployments where the tests run before the registry has finished deploying.

In order to enable this feature, an environment variable PROBE_TIMEOUT needs to be added to the acceptance test template with an integer value which represents seconds to wait.

Target Date: 04-05-2023

@michael-valdron michael-valdron self-assigned this Apr 4, 2023
@openshift-ci openshift-ci bot added area/ci area/registry Devfile registry for stacks and infrastructure labels Apr 4, 2023
@michael-valdron
Copy link
Member Author

This is to be added to the Sprint 235 plan as this is an item for tomorrow's production promotion.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ci area/registry Devfile registry for stacks and infrastructure
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant