IBM Wazi for Dev Spaces

What’s inside?

This repository contains the registry, operator, bundle, and index images for IBM Wazi for Dev Spaces.

• IBM Wazi for Dev Spaces – Operator
  • This repository is based off of the upstream Red Hat Dev Spaces Images repository, where the generated output is located in the respective branch for each version.
• IBM Wazi for Dev Spaces – Devfile / IBM Wazi for Dev Spaces – Plug-in
  • You can use the custom devfile and plug-in registry images to tailor your development environment. After you rebuild the registry images with modifications, and push the images into a container registry, you can deploy these images when creating an instance of IBM Wazi for Dev Spaces or apply the images to an existing instance.
  • Stacks or workspace definitions are pre-configured CodeReady Workspaces with a dedicated set of tools that cover different developer personas. For example, you can pre-configure a workbench for testers with only the tools needed for their purposes. You can add new stacks by customizing the IBM Wazi for Dev Spaces devfile and plug-in registry.

IBM Wazi for Dev Spaces

IBM Wazi for Dev Spaces 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 OpenShift Dev Spaces, IBM Wazi for Dev Spaces offers an easy, streamlined onboarding process to provide mainframe developers with the tools they need. Using container technology, IBM Wazi for Dev Spaces brings the necessary tools to the task at hand. IBM Wazi for Dev Spaces is a component shipped with IBM Developer for z/OS Enterprise Edition (IDzEE).

For more benefits of IBM Wazi for Dev Spaces, see the IBM Wazi product page or IDzEE product page.

Details

IBM Wazi for Dev Spaces 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), REXX, 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 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 Code stack
• Leverage the full language support for Ansible and Red Hat Ansible Certified Content for IBM Z to author and execute playbooks to configure z/OS for development. Automate the deployment and configuration of tools and dependencies such as build, test and debug, to quickly build, deploy and run your applications.

Documentation

For details of the features for IBM Wazi for Dev Spaces, see its official documentation.

Image Information

• catalog Image – This is an index image used for the operator hub.
• operator Image – This is the operator image inherited by Red Hat.
• dev-file Image – This is a customized dev-file registry image.
• plugin Image – This is a customized plugin registry image.
• codeready Image – This is a Wazi sidecar image used to provide supporting resources.

Feedback

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

Reference: Red Hat content

Links marked with this icon 🚪 are internal to Red Hat. This includes Jenkins servers, job configs in gitlab, and container sources in dist-git.

Because these services are internal, in the interest of making all things open, we’ve copied as much as possible into this repo. Details below.

Midstream code

This repo is used to house identical copies of the code used to build the CodeReady Workspaces images in Brew/OSBS, but made public to enable pull requests and easier contribution.

• Downstream code can be found in repos internal to Red Hat at http://pkgs.devel.redhat.com/cgit/?q=codeready-workspaces 🚪
  • select the crw-2-rhel-8 branch for the latest 2.x synced from upstream main branches, or
  • select a branch like crw-2.8-rhel-8 for a specific release, synced to a stable branch like 7.28.x.

Generated code

In some cases, where we need to house code generated by downstream processes in a public location, this repo will contain folders that end in -generated to differentiate from code that’s synced from upstream and copied to downstream.

• codeready-workspaces-operator-metadata-generated/manifests contains CSVs with pinned digests 🚪, generated from downstream Brew processes.

Jenkins jobs

This repo also contains an identical copy of the Jenkinsfiles and groovy 🚪 sources used to configure the jenkins-csb 🚪 Configuration-as-Code (casc) Jenkins instance used to build the artifacts needed for Brew/OSBS builds. Since the server and config sources are internal to Red Hat, this copy is provided to make it easier to see how CodeReady Workspaces is built. Hooray for open source!

• To run a local Jenkins, see README 🚪
• Job 🚪 that performs the sync from gitlab 🚪 to github at intervals
• Other jobs are used to:
  • build a series of artifact and container builds,
  • sync midstream to downstream,
  • build artifacts,
  • orchestrate Brew builds,
  • copy containers to quay,
  • check & update digests in registries/metadata images
• Or, to:
  • send email notifications of ER and RC builds
  • tag sources & collect manifests, collect sources to create a release
  • set up subsequent releases (branching, bumping versions)

GitHub

View Github