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

Centralize DevWorkspace Happy Path test #20421

Closed
sleshchenko opened this issue Sep 6, 2021 · 0 comments
Closed

Centralize DevWorkspace Happy Path test #20421

sleshchenko opened this issue Sep 6, 2021 · 0 comments
Assignees
Labels
area/qe engine/devworkspace Issues related to Che configured to use the devworkspace controller as workspace engine. kind/task Internal things, technical debt, and to-do tasks to be performed. sprint/current
Milestone

Comments

@sleshchenko
Copy link
Member

sleshchenko commented Sep 6, 2021

Is your task related to a problem? Please describe

The problem is that currently there are 3 targets for DevWorkspace Happy path test run by Prow:

And they duplicate some resources, which means - when you need to fix some even minor stuff, like devfile/project which should be used for testing, you need to propagate it to all consumers.

Describe the solution you'd like

Setting up the infrastrucure (deploying Che, DWO) is on consumer side, but tests logic - how to run it, which image to use, which devfile to use should be centralized somehow.

Describe alternatives you've considered

No response

Additional context

No response

@sleshchenko sleshchenko added kind/task Internal things, technical debt, and to-do tasks to be performed. area/devworkspace-operator engine/devworkspace Issues related to Che configured to use the devworkspace controller as workspace engine. team/controller labels Sep 6, 2021
@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 Sep 6, 2021
@RomanNikitenko RomanNikitenko removed the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Sep 7, 2021
@sleshchenko sleshchenko added this to the 7.37 milestone Sep 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/qe engine/devworkspace Issues related to Che configured to use the devworkspace controller as workspace engine. kind/task Internal things, technical debt, and to-do tasks to be performed. sprint/current
Projects
None yet
Development

No branches or pull requests

4 participants