A Clojure S2I Builder for OpenShift

Clojure_logo

In this quickstart, learn how to run Clojure on OpenShift with a custom Source-to-Image (S2I) builder image using OpenShift’s incremental build capability and in an environment where all actions are taken inside OpenShift, except the editing of Clojure code.

Read More...

Jupyter on OpenShift Part 3: Creating a S2I Builder Image

Jupyter on OpenShift Part 3: Creating a S2I Builder Image

In the prior post in this series I described the steps required to run the Jupyter Notebook images supplied by the Jupyter Project developers. When run, these notebook images provide an empty workspace with no initial notebooks to work with. Depending on the image used, they would include a range of pre-installed Python packages, but they may not have all packages installed that a user needs.

Read More...

OpenShift Pipelines with Jenkins Blue Ocean

OpenShift Pipelines with Jenkins Blue Ocean

Jenkins Blue Ocean is the new user experience for Jenkins to provide more flexibility for building and interacting with CI/CD pipelines. Using OpenShift certified Jenkins docker image and S2I process for customizing Jenkins, Blue Ocean can easily be enabled on Jenkins on OpenShift.

Read More...

Red Hat Brings Cloud Native Services to Every Java Workload

Red Hat Brings Cloud Native Services to Every Java Workload

Red Hat is happy to announce the availability of a Java container image for cloud native workloads. Red Hat now expands the availability of cloud native packaging models to all Java applications that rely on OpenJDK and Maven. This builds on the proven S2I technology that has been available for OpenShift applications for many years.

Read More...

Maven Multi-Module Projects and OpenShift

Maven Multi-Module Projects and OpenShift

There is no need to move away from Maven’s multi-module approach to building and deploying application when working with OpenShift, if that is a process you’re familiar with. It can become a powerful tool for helping break apart existing applications into more consumable microservices as it goes some way to enabling each component to have its own lifecycle, regardless of how the source code repository is managed. Sometimes it may require a little bit of customisation to give you the behaviour you need, and hopefully you’ll get some insight into how that customisation is achieved through this post.

Read More...