Chapter 7. Known issues
7.1. Cloning private Git repositories is failing for specified Git revisions
There is currently a known issue when starting workspaces that clone private Git repositories. After successfully cloning and reading the remote Git repository, the project-clone container fails to checkout a specified Git revision, for example a feature branch or PR branch. As a result of this error, the remote Git repository is cloned into a temporary directory named project-clone-<random_characters>.
In OpenShift Dev Spaces, users have two ways to specify a Git revision for a new workspace:
-
By adding a
checkoutFrom
section in the devfile. - By visiting or entering the URL of a feature branch or pull request in the browser or in the OpenShift Dev Spaces dashboard.
Workaround
If you are using a
checkoutFrom
section in the devfile, then do as follows:-
Before starting a new workspace, remove or comment out the
checkoutFrom
section from the devfile. - After the repository is cloned, switch to the desired revision.
-
Before starting a new workspace, remove or comment out the
If you are using the URL of a feature branch or pull request to start a new workspace, then do as follows:
- When starting a new workspace, enter the URL of the repository without any branch syntax.
- After the repository is cloned, switch to the desired revision.
Additional resources
7.2. Java Gradle sample fails in restricted environments
Currently, there is a known issue with the Java Gradle sample in restricted environments. Running the 1-build
command to build an application might result in the FAILURE: Build failed with an exception error and failure to load a native library or not resolving a plug-in artifact in plug-in repositories. There is currently no workaround for this issue.
Additional resources