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

Verify that plugin images referenced in the plugin registry actually exist in Quay #16501

Closed
nickboldt opened this issue Mar 31, 2020 · 4 comments
Assignees
Labels
area/ci CI build and releases, PR testing, & whitelabel/productization issues area/plugin-registry kind/enhancement A feature request - must adhere to the feature request template.
Milestone

Comments

@nickboldt
Copy link
Contributor

Is your enhancement related to a problem? Please describe.

Describe the solution you'd like

we should have better tests in the plugin registry publishing process (and its build too!) to validate that when we add a new plugin 7.9.2 or 7.11.0 for machine-exec and che-theia that the plugins actually exist in quay

This probably requires nothing more than a quick skopeo check:

skopeo inspect docker://quay.io/eclipse/che-*:${VERSION} | grep "${VERSION}"

If found, contrinue the release/build. If not, wait 5 mins and try again... then fail if not found.

TBH I'm not 100% what workflow we want here for if-not-found-then. I guess it will depend on if this is a temporary state (upstream publishing job not yet done; quay.io temporarily down) or a permanent state (we forgot to add the plugin).

This could be as simple as checking ONLY the che-machine-exec and che-theia images, or it could be extended to validate that ALL image references are valid.

See also #16499

@nickboldt nickboldt added the kind/enhancement A feature request - must adhere to the feature request template. label Mar 31, 2020
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Mar 31, 2020
@skabashnyuk skabashnyuk added area/ci CI build and releases, PR testing, & whitelabel/productization issues area/plugin-registry and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Mar 31, 2020
@nickboldt nickboldt added this to the 7.18 milestone Aug 5, 2020
@ericwill
Copy link
Contributor

I think this one can be partially solved by PR checks on the plugin registry, so that non-existent images don't get placed in the registry meta.yaml files. Though I suppose those images could be deleted between merge and release time, so double checking is probably required.

@nickboldt
Copy link
Contributor Author

@ericwill have you implemented anything in the plugin or devfile registries that verify all references images exist?

@ericwill
Copy link
Contributor

@ericwill have you implemented anything in the plugin or devfile registries that verify all references images exist?

The plugin registry has some checks, but nothing comprehensive. It's still a TODO.

@nickboldt
Copy link
Contributor Author

nickboldt commented Feb 8, 2021

Plugin registry now includes digests, so we check that the ref'd images exist in order to fetch digest from tag.

Also: #18747

Eric said:

devfile registry build will fail if any of the base images are missing, so I'm not sure we have the same problem there
that issue was more about meta.yaml's referencing things that don't exist, which we've solved

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ci CI build and releases, PR testing, & whitelabel/productization issues area/plugin-registry kind/enhancement A feature request - must adhere to the feature request template.
Projects
None yet
Development

No branches or pull requests

4 participants