ibm / wazi-codeready-workspaces-operator Goto Github PK

This repository contains a Docker image that packages all the operator lifecycle manager dependencies for installing IBM Wazi Developer for Red Hat CodeReady Workspaces (IBM Wazi Developer for Workspaces). This operator is installed into a Red Hat OpenShift Container Platform for a cluster administrator to manage. Once an instance is deployed into a cluster, then a user can use a browser to access IBM Wazi Developer for Workspaces.

This repository is based off of the upstream Red Hat CodeReady for Workspaces Operator, whose code is in another upstream Eclipse Che Operator repository. Repositories gathered together downstream are all brought together into a Red Hat CodeReady Workspaces Images repository, where the generated output is located in the respective branch for each version.

IBM Wazi Developer for Workspaces is a component shipped with either IBM Wazi Developer for Red Hat CodeReady Workspaces (Wazi Developer for Workspaces) or IBM Developer for z/OS Enterprise Edition (IDzEE).

IBM Wazi Developer for Workspaces provides a modern experience for mainframe software developers working with z/OS applications in the cloud. Powered by the open source projects Zowe and Red Hat CodeReady Workspaces, IBM Wazi Developer for Workspaces offers an easy, streamlined onboarding process to provide mainframe developers the tools they need. Using container technology, IBM Wazi Developer for Workspaces brings the necessary tools to the task at hand.

For more benefits of IBM Wazi Developer for Workspaces, see the IBM Wazi Developer product page or IDzEE product page.

IBM Wazi Developer for Workspaces provides a custom stack with the all-in-one mainframe development package that enables mainframe developers to:

• Use a modern mainframe editor with rich language support for COBOL, JCL, Assembler (HLASM), and PL/I, which provides language-specific features such as syntax highlighting, outline view, declaration hovering, code completion, snippets, a preview of copybooks, copybook navigation, and basic refactoring using IBM Z Open Editor, a component of IBM Wazi Developer for VS Code
• Integrate with any flavor of Git source code management (SCM)
• Perform a user build with IBM Dependency Based Build for any flavor of Git
• Work with z/OS resources such as MVS, UNIX files, and JES jobs
• Connect to the Z host with z/OSMF or IBM Remote System Explorer (RSE) API, using Zowe Explorer plus IBM Z Open Editor for a graphical user interface and Zowe CLI plus the RSE API plug-in for Zowe CLI for command line access
• Debug COBOL and PL/I applications using IBM Z Open Debug
• Use a mainframe development package with a custom plug-in and devfile registry support from the IBM Wazi Developer stack

For details of the features for IBM Wazi Developer for Workspaces, see its official documentation.

We would love to hear feedback from you about IBM Wazi Developer for Workspaces.
File an issue or provide feedback here: IBM Wazi Developer for Workspaces Issues

• The CRW operator has most of code in the upstream che-operator repo, including this Dockerfile.

• This code is then synced to the downstream repo via a job located here:

  • https://main-jenkins-csb-crwqe.apps.ocp4.prod.psi.redhat.com/job/CRW_CI/ (jobs)
  • https://gitlab.cee.redhat.com/codeready-workspaces/crw-jenkins/-/tree/master/jobs/CRW_CI (sources)
  • https://github.com/redhat-developer/codeready-workspaces-images#jenkins-jobs (copied sources)

The Jenkinsfile transforms the Che code into CRW code and commits the changed code directly to downstream so there's no need for a branch in che-operator or to have code duplicated here.

• Once the sync is done:

  • the codeready-workspaces-operator repo is updated;

  • a Brew build will be triggered via get-sources-rhpkg-container-build job

  • and, if successful, the Brew build will be copied to Quay as https://quay.io/crw/crw-2-rhel8-operator.

• Metadata for the CRW operator is contained in this repo. See manifests, metadata and deploy folders, and this operator-metadata.Dockerfile.

• The metadata is then synced to the downstream repo via a job located here:

  • https://main-jenkins-csb-crwqe.apps.ocp4.prod.psi.redhat.com/job/CRW_CI/ (jobs)
  • https://gitlab.cee.redhat.com/codeready-workspaces/crw-jenkins/-/tree/master/jobs/CRW_CI (sources)
  • https://github.com/redhat-developer/codeready-workspaces-images#jenkins-jobs (copied sources)

• Once the sync is done:

  • the codeready-workspaces-operator-metadata repo is updated;

  • a Brew build will be triggered via get-sources-rhpkg-container-build job

  • and, if successful, the Brew build will be copied to Quay] as https://quay.io/crw/crw-2-rhel8-operator-metadata.

• Once the operator and metadata is rebuilt, a new build of crwctl is triggered.

• This is triggered because the CRW operator-metadata's deploy folder is used in crwctl to do deployment when there is no OLM present on the target cluster (OCP 3.11 and 4.1).

See crwctl job located here:

• https://main-jenkins-csb-crwqe.apps.ocp4.prod.psi.redhat.com/job/CRW_CI/ (jobs)
• https://gitlab.cee.redhat.com/codeready-workspaces/crw-jenkins/-/tree/master/jobs/CRW_CI (sources)
• https://github.com/redhat-developer/codeready-workspaces-images#jenkins-jobs (copied sources)