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

Improve docs and devfile on workspace loader development flow #15125

Merged
merged 1 commit into from
Nov 6, 2019

Conversation

mmorhun
Copy link
Contributor

@mmorhun mmorhun commented Nov 6, 2019

What does this PR do?

Improves docs in CONTRIBUTING.md file which describes development and testing flow of workspace loader.
Also adds sparse checkout parameter into the workspace loader devfile to have only workspace loader source code instaed of whole Che repository.

@mmorhun mmorhun self-assigned this Nov 6, 2019
@mmorhun mmorhun added the area/doc Issues related to documentation label Nov 6, 2019
@che-bot che-bot added the status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. label Nov 6, 2019
@che-bot
Copy link
Contributor

che-bot commented Nov 6, 2019

✅ E2E Happy path tests succeed 🎉

See Details

Tested with Eclipse Che Single User on K8S (minikube v1.1.1)

CONTRIBUTING.md Outdated Show resolved Hide resolved
CONTRIBUTING.md Outdated

To be able to point new workspace loader to the test workspace it is required to add the the test workspace id to the path of workspace loader route.
So, first, we need to retrieve the test workspace id.
This could be done using swagger (please note, it might be disable on production environment).
Copy link
Contributor

@AndrienkoAleksandr AndrienkoAleksandr Nov 6, 2019

Choose a reason for hiding this comment

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

User could grab workspaceId like env variable from any workspace container, so maybe it is better to apply this information instead of swagger.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, this is useful information, however requires to have running workspace. I think it would be better to not to require running state of the test workspace (because in many cases workspace loader should be tested with workspace start flow).

@che-bot
Copy link
Contributor

che-bot commented Nov 6, 2019

E2E tests of Eclipse Che Multiuser on OCP has been successful:

@mmorhun mmorhun force-pushed the improve-docs-ws-loader-dev-flow branch from 59101e7 to e512b53 Compare November 6, 2019 13:08
@che-bot
Copy link
Contributor

che-bot commented Nov 6, 2019

✅ E2E Happy path tests succeed 🎉

See Details

Tested with Eclipse Che Single User on K8S (minikube v1.1.1)

Signed-off-by: Mykola Morhun <mmorhun@redhat.com>
@mmorhun mmorhun force-pushed the improve-docs-ws-loader-dev-flow branch from e512b53 to 267c1aa Compare November 6, 2019 13:40
@che-bot
Copy link
Contributor

che-bot commented Nov 6, 2019

✅ E2E Happy path tests succeed 🎉

See Details

Tested with Eclipse Che Single User on K8S (minikube v1.1.1)

@che-bot
Copy link
Contributor

che-bot commented Nov 6, 2019

E2E tests of Eclipse Che Multiuser on OCP has been successful:

@mmorhun mmorhun merged commit 98e2487 into master Nov 6, 2019
@mmorhun mmorhun deleted the improve-docs-ws-loader-dev-flow branch November 6, 2019 15:10
@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 Nov 6, 2019
@che-bot che-bot added this to the 7.4.0 milestone Nov 6, 2019
skabashnyuk pushed a commit to skabashnyuk/che that referenced this pull request Mar 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/doc Issues related to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants