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.
Che Server is mostly a Java web application deployed on an Apache Tomcat server in a container. Che Server uses the following modules:
- 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
- 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
- infrastructures/kubernetes
- infrastructure/openshift
- infrastructures/infrastructure-factory
Other modules are deprecated and will be removed in the future.
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.
The che-server builds are revved up by Develocity, which enhances developer productivity through features such as Build Scan for build insights and collaborative troubleshooting, and remote Build Cache for build acceleration. Develocity also provides comprehensive reporting and visualization of build data.
To view the Build Scan produced by a build, click on the generated link at the end of the build. Build Scans are available locally and on GitHub Action CI (limited to users authenticated to publish local scans). You can access all scans published by the che-server builds on the Eclipse Develocity dashboard by searching for the che server project.
Here are additional useful links with the che-server builds data:
- Build Scans
- Trends dashboard
- Failures dashboard
- Failed and flaky Tests dashboard