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

[TS_SELENIUM] Create image for the "Happy Path" tests based on the "quay.io/eclipse/che-java11-maven" image #14737

Closed
Ohrimenko1988 opened this issue Oct 2, 2019 · 3 comments
Assignees
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed.

Comments

@Ohrimenko1988
Copy link
Contributor

Ohrimenko1988 commented Oct 2, 2019

Is your task related to a problem? Please describe.

Currently, for the "Happy Path" scenario used a docker image without real user. It may lead to the problem described in the issue #14722 .

Describe the solution you'd like

Create an image for the "Happy Path" tests based on the "quay.io/eclipse/che-java11-maven" image

Describe alternatives you've considered

Additional context

@Ohrimenko1988 Ohrimenko1988 added status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. kind/task Internal things, technical debt, and to-do tasks to be performed. team/che-qe labels Oct 2, 2019
@Ohrimenko1988 Ohrimenko1988 self-assigned this Oct 2, 2019
@rhopp
Copy link
Contributor

rhopp commented Oct 2, 2019

@Ohrimenko1988 @musienko-maxim Didn't we bundle mvn deps into this image to speed up the test exectuion?
If yes, we need to rebuild the image and while doing that, we should push it to some "general" image registry, instead of bujhtr5555 (whose is this anyway?).
And we need to rebuild this image with every version of quay.io/eclipse/che-java11-maven (as part of the che build/release process?)

@Ohrimenko1988
Copy link
Contributor Author

Ohrimenko1988 commented Oct 2, 2019

@rhopp Yes, I described this in the comment
#14722 (comment)

@Ohrimenko1988 Ohrimenko1988 added status/in-progress This issue has been taken by an engineer and is under active development. and removed status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. labels Oct 2, 2019
@Ohrimenko1988 Ohrimenko1988 added status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. and removed status/in-progress This issue has been taken by an engineer and is under active development. labels Oct 4, 2019
@Ohrimenko1988 Ohrimenko1988 removed the status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. label Oct 16, 2019
@Ohrimenko1988
Copy link
Contributor Author

Done #14779

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed.
Projects
None yet
Development

No branches or pull requests

2 participants