|
Note
|
the so-called master branch is deprecated and is no longer kept up to date. Instead, the latest nightly sources are in crw-2-rhel-8 branch, synced to upstream projects' main (or master) branches. |
For the latest stable release, see the crw-2.y-rhel-8 branch with the largest y value.
This repository hosts CodeReady Workspaces assembly that mainly inherits Eclipse Che artifacts and repackages some of them:
Differences as compared to upstream:
-
Customized Dashboard (pics, icons, titles, loaders, links)
-
Samples and Stacks modules
-
Bayesian Language Server and agent
-
Product Info plugin (IDE customizations: pics, titles links)
-
Custom Dockerfile based on official RH OpenJDK image from RHCC
|
Note
|
Dockerfiles in this repo are NOT the ones used to build RHCC container images in OSBS. |
Run the following command in the root of a repository:
mvn clean installThe build artifact used in the container image will be in assembly/codeready-worksapces-assembly-main/target
First, build the CRW assembly in this repo:
mvn clean installThen just use the Dockerfile in this repo to build:
podman build --force-rm -t registry.redhat.io/codeready-workspaces/server-rhel8:2.y . && \
podman images | grep registry.redhat.io/codeready-workspaces/server-rhel8:2.yYou can then reference this image in your deployment (set image pull policy to Always to make sure it’s pulled instead of the default one).
For more info on how to test locally built changes in a local OKD 3.11 (Minishift 1.34) cluster, see Build CodeReady Workspaces server container locally and deploy using Minishift.
|
Note
|
Once published, images will be in locations like these:
|
See this document for how to use those build systems, in order to publish a container image to Red Hat Container Catalog:
See also:
If you have access to Red Hat VPN, clone the pkgs.devel repo, then run the get-sources-jenkins.sh script to pull the latest dependency tarball into the local project, and trigger a Brew build.
kinit
git clone ssh://kerberos-username@pkgs.devel.redhat.com/containers/codeready-workspaces
cd codeready-workspaces
./get-sources-jenkins.shUpstream: https://github.com/eclipse/che Midstream: (this repo) Downstream: http://pkgs.devel.redhat.com/cgit/containers/codeready-workspaces/tree/?h=crw-2-rhel-8
Sync jobs:
The Jenkinsfile in this repo has moved. See:
Folders under /dependencies are synced to https://github.com/redhat-developer/codeready-workspaces-images. If no matching project exists under the /dependencies folder, sync occurs directly from an upstream Che project.
Sync jobs:
These files have moved, as they sync directly from an upstream repo:
-
dependencies/che-jwtproxy/Jenkinsfile
-
dependencies/che-machine-exec/Jenkinsfile
-
dependencies/che-pluginbroker/Jenkinsfile
-
dependencies/configbump/Jenkinsfile
-
dependencies/kubernetes-image-puller/Jenkinsfile
-
dependencies/push-latest.Jenkinsfile
-
dependencies/send-email-qe-build-list.Jenkinsfile
-
dependencies/traefik/Jenkinsfile
-
dependencies/update-digests.Jenkinsfile
Branding is currently in two places.
To reskin the Che server assembly, you need to edit the following files, which are used in the Che Dashboard:
-
assembly/branding/branding-crw.css - replacement for Che default css, copied via Jenkinsfile during Pipeline build
-
assembly/branding/product.json.template
-
assembly/branding/favicon.ico - browser tab favicon
-
assembly/branding/che-logo-text.svg - top left wordmark
-
assembly/branding/che-logo.svg - bottom left icon
-
assembly/branding/loader.svg - dashboard loading animation
-
See also SVG assets in product/branding/ folder.
|
Note
|
In a future release, the Che Dashboard will be a separate deployment from the Che Server, which means the above information may become incorrect. |
In addition to the Che Dashboard branding, there is also branding elements for Che Theia. See details in codeready-workspaces-theia/conf/theia/branding.