You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: README.adoc
+6-6
Original file line number
Diff line number
Diff line change
@@ -4,13 +4,13 @@ Because these services are internal, in the interest of making all things open,
4
4
5
5
## What's inside?
6
6
7
-
NOTE: the so-called master branch is deprecated and is no longer kept up to date. Instead, the latest nightly sources are in **devspaces-3-rhel-8 branch**, synced to upstream projects' main (or master) branches.
7
+
NOTE: the so-called master branch is deprecated and is no longer kept up to date. Instead, the latest nightly sources are in **devspaces-3-rhel-9 branch**, synced to upstream projects' main (or master) branches.
8
8
9
-
For the latest stable release, see the **devspaces-3.y-rhel-8** branch with the largest y value.
9
+
For the latest stable release, see the **devspaces-3.y-rhel-9** branch with the largest y value.
10
10
11
11
---
12
12
13
-
This repository no longer hosts the OpenShift Dev Spaces Server assembly that mainly inherits Eclipse Che artifacts and repackages some of them. Server has moved to link:https://github.com/redhat-developer/devspaces-images/blob/devspaces-3-rhel-8/devspaces-server/README.adoc#how-to-build-locally[devspaces-images/devspaces-server].
13
+
This repository no longer hosts the OpenShift Dev Spaces Server assembly that mainly inherits Eclipse Che artifacts and repackages some of them. Server has moved to link:https://github.com/redhat-developer/devspaces-images/blob/devspaces-3-rhel-9/devspaces-server/README.adoc#how-to-build-locally[devspaces-images/devspaces-server].
14
14
15
15
### How to Build DS Containers Using casc Jenkins (REQUIRES VPN)
16
16
@@ -29,9 +29,9 @@ Folders under link:dependencies[/dependencies] are synced to https://github.com/
29
29
30
30
The sync logic is in one of three places:
31
31
32
-
* a Jenkins job - eg., link:https://github.com/redhat-developer/devspaces-images/blob/devspaces-3-rhel-8/crw-jenkins/jobs/DS_CI/dashboard_3.x.jenkinsfile[dashboard_3.x.jenkinsfile],
33
-
* a get-sources.sh script - eg., link:https://github.com/redhat-developer/devspaces-images/blob/devspaces-3-rhel-8/devspaces-dashboard/get-sources.sh[dashboard get-sources.sh], or
34
-
* a sync-*.sh script - eg., link:https://github.com/redhat-developer/devspaces-images/blob/devspaces-3-rhel-8/devspaces-dashboard/build/scripts/sync.sh[dashboard/scripts/sync.sh].
32
+
* a Jenkins job - eg., link:https://github.com/redhat-developer/devspaces-images/blob/devspaces-3-rhel-9/crw-jenkins/jobs/DS_CI/dashboard_3.x.jenkinsfile[dashboard_3.x.jenkinsfile],
33
+
* a get-sources.sh script - eg., link:https://github.com/redhat-developer/devspaces-images/blob/devspaces-3-rhel-9/devspaces-dashboard/get-sources.sh[dashboard get-sources.sh], or
34
+
* a sync-*.sh script - eg., link:https://github.com/redhat-developer/devspaces-images/blob/devspaces-3-rhel-9/devspaces-dashboard/build/scripts/sync.sh[dashboard/scripts/sync.sh].
35
35
36
36
Note over time we're trying to move all sync logic out of Jenkinsfiles and into scripts that can be run locally, so during outages build process can still be orchestrated. Goal is to have Jenkins simply call sync.sh scripts to perform syncs, and get-sources.sh scripts to collect assets from Jenkins (or other places) in order to commit those source tarballs + trigger Brew builds.
Copy file name to clipboardexpand all lines: dependencies/che-plugin-registry/README.md
+6-6
Original file line number
Diff line number
Diff line change
@@ -11,17 +11,17 @@ Luckily there is an automatic way to build and publish .vsix files and their sou
11
11
## Plugin Registry Build Process
12
12
The DS plugin registry is a fork of the upstream [Che plugin registry](https://github.com/eclipse-che/che-plugin-registry). While the build logic to build the actual registry is very similar to upstream, the steps required to actually build + publish the DS plugin registry images is quite different.
13
13
14
-
To build the devfile registry for use with a specific Dev Spaces 3.yy version, it is necessary to check out the appropriate `devspaces-3.yy-rhel-8` branch. This will ensure the build contains the correct tags and references to the images. The `devspaces-3-rhel-8` branch is for the upcoming 3.next release.
14
+
To build the devfile registry for use with a specific Dev Spaces 3.yy version, it is necessary to check out the appropriate `devspaces-3.yy-rhel-9` branch. This will ensure the build contains the correct tags and references to the images. The `devspaces-3-rhel-9` branch is for the upcoming 3.next release.
15
15
16
16
### Local DS Plugin Registry Build Process
17
17
A local build works just like upstream -- use the `build.sh` script. The only difference in DS is that the resulting devfile.yaml files generated by the build process are zipped up into a .tar.gz file and copied into the container. This differs from upstream which just copies the output folder directly.
18
18
The default `OpenVSX` version used is `che-openvsx`, which will be built from https://github.com/che-incubator/che-openvsx.git at a tag defined in the [job-config.json](../job-config.json). To override this version use the `--che-openvsx-url` parameter in `build.sh` to set a URL where alternative `OpenVSX` sources can be downloaded. The URL must point to a file named `che-openvsx.tar.gz`.
19
19
20
20
### DS Plugin Registry Build/Publish
21
21
All contributions to the DS plugin registry should land in this repository. From there on, the following things happen:
22
-
1. Code in this repository is synchronized from this repo to the [plugin registry directory in the devspaces-images repository](https://github.com/redhat-developer/devspaces-images/tree/devspaces-3-rhel-8/devspaces-pluginregistry) by a [Jenkins job](https://main-jenkins-csb-crwqe.apps.ocp-c1.prod.psi.redhat.com/job/DS_CI/job/pluginregistry_3.x).
23
-
2. The job from step `1.` kicks off a subsequent [Jenkins job](https://main-jenkins-csb-crwqe.apps.ocp-c1.prod.psi.redhat.com/job/DS_CI/job/sync-to-downstream_2.x) that then runs the bootstrap build, which uses the sync'd code in [devspaces-images repository](https://github.com/redhat-developer/devspaces-images/tree/devspaces-3-rhel-8/devspaces-pluginregistry). The boostrap build builds the plugin registry in offline mode, using tagged image references. The resulting binaries and meta.yaml files are placed in a .tar.gz archive and the archive is committed to rhpkg for later usage in Brew.
24
-
3. If step `2.` is successful then a Brew build is kicked off. The Brew build copies the generated content in the .tar.gz archive from step `2.` into the [Dockerfile](https://github.com/redhat-developer/devspaces/blob/devspaces-3-rhel-8/dependencies/che-plugin-registry/build/dockerfiles/Dockerfile) and completes the last stages of the plugin registry build.
22
+
1. Code in this repository is synchronized from this repo to the [plugin registry directory in the devspaces-images repository](https://github.com/redhat-developer/devspaces-images/tree/devspaces-3-rhel-9/devspaces-pluginregistry) by a [Jenkins job](https://main-jenkins-csb-crwqe.apps.ocp-c1.prod.psi.redhat.com/job/DS_CI/job/pluginregistry_3.x).
23
+
2. The job from step `1.` kicks off a subsequent [Jenkins job](https://main-jenkins-csb-crwqe.apps.ocp-c1.prod.psi.redhat.com/job/DS_CI/job/sync-to-downstream_2.x) that then runs the bootstrap build, which uses the sync'd code in [devspaces-images repository](https://github.com/redhat-developer/devspaces-images/tree/devspaces-3-rhel-9/devspaces-pluginregistry). The boostrap build builds the plugin registry in offline mode, using tagged image references. The resulting binaries and meta.yaml files are placed in a .tar.gz archive and the archive is committed to rhpkg for later usage in Brew.
24
+
3. If step `2.` is successful then a Brew build is kicked off. The Brew build copies the generated content in the .tar.gz archive from step `2.` into the [Dockerfile](https://github.com/redhat-developer/devspaces/blob/devspaces-3-rhel-9/dependencies/che-plugin-registry/build/dockerfiles/Dockerfile) and completes the last stages of the plugin registry build.
25
25
26
26
## Building and Publishing Third Party Binaries for Plugin Registry Sidecar Containers
27
27
@@ -33,8 +33,8 @@ Sidecar image sources are then synced from the [devspaces-images](https://github
Copy file name to clipboardexpand all lines: product/branding/README.adoc
+2-2
Original file line number
Diff line number
Diff line change
@@ -8,9 +8,9 @@ Branding is currently in two places.
8
8
9
9
### Dashboard
10
10
11
-
To reskin link:https://github.com/eclipse-che/che-dashboard[Che Dashboard], see link:https://github.com/redhat-developer/devspaces-images/tree/devspaces-3-rhel-8/devspaces-dashboard/README.adoc[dashboard].
11
+
To reskin link:https://github.com/eclipse-che/che-dashboard[Che Dashboard], see link:https://github.com/redhat-developer/devspaces-images/tree/devspaces-3-rhel-9/devspaces-dashboard/README.adoc[dashboard].
12
12
13
13
### Microsoft Visual Studio Code - Open Source IDE
14
14
15
-
To reskin link:https://github.com/che-incubator/che-code/[che-code], which is built from link:https://github.com/microsoft/vscode[Microsoft Visual Studio Code - Open Source IDE], see https://github.com/redhat-developer/devspaces-images/tree/devspaces-3-rhel-8/devspaces-code/branding[devspaces-images/devspaces-code/branding].
15
+
To reskin link:https://github.com/che-incubator/che-code/[che-code], which is built from link:https://github.com/microsoft/vscode[Microsoft Visual Studio Code - Open Source IDE], see https://github.com/redhat-developer/devspaces-images/tree/devspaces-3-rhel-9/devspaces-code/branding[devspaces-images/devspaces-code/branding].
0 commit comments