Go to file

Igor Vinokur da5174bf17 Duplicate creating a git-credentials secret on token fetch (#551 ) Duplicate the git-credentials secret creation step on create personal access token secret. Currently this step is performed on workspace provision step but in this case the PAT secret might be initialised when the provision is finished. In order to synchronise the personal access token secret and git credentials secret creation step duplicate the git credentials secret creation step after the PAT secret creation step. Refactor the get(scmServerUrl) function in the KubernetesPersonalAccessTokenManager class		2023-09-05 12:49:09 +03:00
.ci/openshift-ci	Provision git credentials secrets on workspace start (#527 )	2023-06-26 17:18:32 +03:00
.github	22407 - Remove Mattermost notification (#544 )	2023-08-17 09:28:20 +02:00
.mvn	Set up maven build of core, plugins, dashboard, assembly	2016-02-12 09:47:39 +02:00
.vscode	Add .vscode/settings.json with java settings (#524 )	2023-06-14 10:14:24 +03:00
assembly	Support SSH urls (#539 )	2023-08-27 16:17:13 +03:00
core	Set original message and stack trace to a Runtime Exception DTO (#550 )	2023-08-30 09:35:08 +03:00
deploy/cert-manager	Remove the Helm chart.	2022-06-25 07:49:09 +09:00
dockerfiles	chore: Update from ubi8-minimal:8.8-1014 to ubi8-minimal:8.8-1037 (#542 )	2023-08-14 14:47:03 -07:00
docs	feat: add OpenShift web console dashboard definition	2023-04-17 15:37:16 +02:00
infrastructures	Duplicate creating a git-credentials secret on token fetch (#551 )	2023-09-05 12:49:09 +03:00
multiuser	chore: Bump to 7.74.0-SNAPSHOT in main	2023-08-23 15:09:29 +02:00
typescript-dto	chore: Bump to 7.74.0-SNAPSHOT in main	2023-08-23 15:09:29 +02:00
wsmaster	Duplicate creating a git-credentials secret on token fetch (#551 )	2023-09-05 12:49:09 +03:00
.gitattributes	Add typescript	2016-08-09 06:29:32 -07:00
.gitignore	Create tests for the "Typescript" and "Node-debug2" plugins (#19474 )	2021-04-01 21:07:14 +03:00
LICENSE	Fix remaining notes about old EPL 1.0 license (#10607 )	2018-08-01 09:48:15 +03:00
NUMBERING.md	Set up maven build of core, plugins, dashboard, assembly	2016-02-12 09:47:39 +02:00
README.md	Update the `Readme.md` with build and debug instructions (#503 )	2023-04-20 10:07:54 +03:00
RELEASE.md	Update README.md and RELEASE.md (#19560 )	2021-04-14 08:45:41 -04:00
check_properties_description.sh	Properties script (#19253 )	2021-03-16 12:04:53 +02:00
devfile.yaml	chore: devfile update	2023-06-15 10:19:20 +02:00
make-release.sh	chore: always pull before push, and use rebase=true to resolve commits (#445 )	2023-02-15 14:43:46 -04:00
pom.xml	Update io.fabric8.kubernetes-client version to latest (#549 )	2023-08-29 16:38:31 +03:00

README.md

What is Che server

Che Server provides an API for managing Kubernetes namespaces, and to retrieve devfile content from repositories, hosted on GitHub, GitLab, Bitbucket, and Microsoft Azure Repos.

Project structure

Che Server is mostly a Java web application deployed on an Apache Tomcat server in a container. Che Server uses the following modules:

OAuth1 / OAuth2 API implementations

wsmaster/che-core-api-auth
wsmaster/che-core-api-azure-devops
wsmaster/che-core-api-bitbucket
wsmaster/che-core-api-github
wsmaster/che-core-api-gitlab

Factory flow implementations

wsmaster/che-core-api-factory-azure-devops
wsmaster/che-core-api-factory-bitbucket
wsmaster/che-core-api-factory-bitbucket-server
wsmaster/che-core-api-factory-github
wsmaster/che-core-api-factory-gitlab
wsmaster/che-core-api-factory-shared

Kubernetes namespace provisioning

infrastructures/kubernetes
infrastructure/openshift
infrastructures/infrastructure-factory

Other modules are deprecated and will be removed in the future.

Build requirements

Apache Maven 3.6.3 or later
JDK 11
Podman or Docker (required for running integration tests)

Sources build

Run mvn clean install to build. Activate a faster profile build by adding -Pfast.

Image build and push

Go to the dockerfiles directory.
Run ./build.sh.
Tag the che-server image with your account: docker tag quay.io/eclipse/che-server:next <docker registry>/<your account>/che-server:next.
Push the che-server image to your account: docker push <docker registry>/<your account>/che-server:next.

Debug

Deploy Che to a Red Hat OpenShift or Minikube cluster by using a previously built image: chectl server:start --platform=<openshift / minikube> --cheimage=<docker registry>/<your account>/che-server:next.
Enable local debugging of the Eclipse Che server: chectl server:debug.
In your IDE, create a new Remote JVM Debug configuration on localhost:8000.
Hit a breakpoint in the code and activate the debug configuration.

CI

There are several GitHub Actions workflows implemented for this repository:

Builds Maven artifacts, builds container images and pushes them to quay.io on each commit to main branch.
Builds Maven artifacts and container images. Images are public and pushed to quay.io. See RELEASE.md for more information about this workflow.
Creates a GitHub release which will include a generated changelog.
Runs on each commit to main branch.
Builds Maven artifacts and container images. This workflow is used as a check for all pull requests that are submitted to this project.
Runs Sonar against the main branch. The result can be seen here.
Used as a check for pull requests that are submitted to this project.

Downstream builds can be found at the link below, which is internal to Red Hat. Stable builds can be found by replacing the 3.x with a specific version like 3.2.

server_3.x

License

Eclipse Public License 2.0

Join the community

The Eclipse Che community is globally reachable through public chat rooms, mailing list and weekly calls. See the Eclipse Che Documentation about how you can join our community.

Report issues

Issues are tracked on the main Eclipse Che Repository: https://github.com/eclipse/che/issues