-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Add sparseCheckoutDir parameter into devfile spec #14823
Conversation
E2E tests of Eclipse Che Multiuser on OCP has failed:
|
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has failed:
|
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has been successful:
|
E2E tests of Eclipse Che Multiuser on OCP has been successful:
|
...ace/src/main/java/org/eclipse/che/api/workspace/server/devfile/convert/ProjectConverter.java
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In general LGTM. Take a look inline comments
...thub/src/main/java/org/eclipse/che/api/factory/server/github/GithubSourceStorageBuilder.java
Show resolved
Hide resolved
wsmaster/che-core-api-workspace/src/main/resources/schema/devfile.json
Outdated
Show resolved
Hide resolved
wsmaster/che-core-api-workspace/src/main/resources/schema/devfile.json
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Documentation changes needed for this pr.
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has been successful:
|
E2E tests of Eclipse Che Multiuser on OCP has failed:
|
direct link to the single failing test: |
the single failing test is DirectUrlFactoryWithSpecificBranchTest.factoryWithDirectUrlWithSpecificBranch which seems to be failing on master too #14842 |
@skabashnyuk here is docs PRs (updated description): But I believe we should not merge them before frontend part of this issue is merged. |
@musienko-maxim could you please test factories scenario against this PR? Also please test factory |
Signed-off-by: Mykola Morhun <mmorhun@redhat.com>
Signed-off-by: Mykola Morhun <mmorhun@redhat.com>
Rebased |
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has been successful:
|
E2E tests of Eclipse Che Multiuser on OCP has been successful:
|
...rkspace/src/test/resources/devfile/schema_test/devfile/devfile_with_sparse_checkout_dir.yaml
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Make sure that you merged before release. Otherwise move migration scripts to 7.4.0 folder
Signed-off-by: Mykola Morhun <mmorhun@redhat.com>
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has been successful:
|
E2E tests of Eclipse Che Multiuser on OCP has failed:
|
ci-test |
E2E tests of Eclipse Che Multiuser on OCP has failed:
|
Test failed because of network issue:
|
ci-test |
E2E tests of Eclipse Che Multiuser on OCP has failed:
|
The DirectUrlFactoryWithSpecificBranchTest was rechecked locally, and passed. |
Signed-off-by: Mykola Morhun mmorhun@redhat.com
What does this PR do?
Adds non mandatory attribute
sparseCheckoutDir
into devfile specification. The attribute is added undersource
section of a project.Adds new
sparse_checkout_dir
column intodevfile_project
table of Che database.What issues does this PR fix or reference?
Implements Che server side of the issue
Release Notes
Added
sparseCheckoutDir
parameter for git type of projectsDocs PR
eclipse-che/che-docs#842
redhat-developer/devfile#53