-
The CRW operator has some of its code in the upstream che-operator repo, including this Dockerfile.
-
This code is then synced to the downstream repo via this job (operator.Jenkinsfile).
Note
|
The job can be configured to sync from any upstream che-operator branch, eg., SOURCE_BRANCH = crw-2.0 or master .
|
-
Once the sync is done:
-
the codeready-workspaces-operator repo is updated;
-
a Brew build will be triggered via this job;
-
and, if successful, the Brew build will be pushed to Quay as
quay.io/crw/operator-rhel8
.
-
-
Metadata for the CRW operator is contained in this repo. See controller-manifests and deploy folders, and this operator-metadata.Dockerfile.
-
The metadata is then synced to the downstream repo via this job (operator-metadata.Jenkinsfile).
Note
|
The job can be configured to sync from any upstream che-operator branch, eg., SOURCE_BRANCH = master .
|
-
Once the sync is done:
-
the codeready-workspaces-operator-metadata repo is updated;
-
a Brew build will be triggered via this job;
-
and, if successful, the Brew build will be pushed to Quay as
quay.io/crw/operator-metadata
.
-