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

Update default plugin/devfile registries to use prod-preview #14267

Merged
merged 1 commit into from
Aug 20, 2019

Conversation

amisevsk
Copy link
Contributor

What does this PR do?

Use https://che-plugin-registry.prod-preview.openshift.io and https://che-devfile-registry.prod-preview.openshift.io/ instead of their production equivalents.

What issues does this PR fix or reference?

#14266, #14261

Update the default registries used in che.properties to use the
prod-preview deployments instead of production. This is to avoid issues
where snapshot changes of registries and che defaults are incompatible
with the deployment on production.

Signed-off-by: Angel Misevski <amisevsk@redhat.com>
@amisevsk amisevsk requested a review from sleshchenko August 16, 2019 17:56
@che-bot che-bot added status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. kind/bug Outline of a bug - must adhere to the bug report template. labels Aug 16, 2019
@che-bot
Copy link
Contributor

che-bot commented Aug 16, 2019

E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has failed:

@che-bot
Copy link
Contributor

che-bot commented Aug 16, 2019

Results of automated E2E tests of Eclipse Che Multiuser on OCP:
Build details
Test report
docker image: eclipseche/che-server:14267
https://github.com/orgs/eclipse/teams/eclipse-che-qa please check this report.

@eclipse-che eclipse-che deleted a comment from che-bot Aug 19, 2019
Copy link
Contributor

@rhopp rhopp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree, this is step in right direction.

@ibuziuk
Copy link
Member

ibuziuk commented Aug 19, 2019

hmm... I thought the plan was not to use OSIO registries at all by default, but rather deploy them together with Che Server

Copy link
Member

@ibuziuk ibuziuk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is it considered to be a temp solution?

Copy link
Member

@ibuziuk ibuziuk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This sounds like a reasonable workaround for minishift addon case. But in general, I do believe upstream che should not fall back on osio plugin registries at all since it makes Hosted Che and Che release process dependent

@amisevsk
Copy link
Contributor Author

@ibuziuk Yeah this is definitely to be a temporary solution, since rolling out nightlies of the registries will only work going forward if we somehow also roll out Che nightlies. I think that after all deployment methods are updated to deploy registries alongside Che, we should leave the che.properties values as NULL.

@amisevsk amisevsk merged commit 29e9dc4 into eclipse-che:master Aug 20, 2019
@che-bot che-bot added this to the 7.1.0 milestone Aug 20, 2019
@che-bot che-bot removed the status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. label Aug 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Outline of a bug - must adhere to the bug report template.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants