Image for post
Image for post
Photo by Caspar Camille Rubin on Unsplash

This is just a short note. Will write more if I find the time.

Sometimes your script needs to know which version of java is currently running on your environment. And on those occasions, I always found myself looking for the all conquering “Eierlegenderwollmilichsau” of methods on the internet. It needed to be:

  • small (a couple of lines, no more)
  • non-intrusive (no added temp files, etc)
  • portable (-ish*)

* in an bash sense at least 😉, although I’m sure there’s a Windows equivalent

There are various ways to do so, such as parsing the version from the java -version command…


Image for post
Image for post

In my last post, Jenkins X — Managing Jenkins, I talked about how we manage our Jenkins server. This time around, I’ll be looking at the Nexus server and how it too can be similarly managed.

Current Status

Jenkins X comes with an optional Nexus server packaged into the platform which is great to get you started. However, as your project becomes more complex, you might find yourself needing other repositories or changes to the configuration. It is these changes which proved a little difficult to manage. Here is the setup as of today:

  • current Jenkins X nexus chart hard-codes the pre-packaged…


Image for post
Image for post

Welcome back to my mini-series on Jenkins X. In the last post I discussed how to enable TLS in your preview environments. This time around we will be discussing the Jenkins server and how we, here at Datameer, manage changes and updates to both jobs and configuration.

I’ll admit, it has taken me a little too long to write this post. Mostly because there are so many aspects and angles to it that I couldn’t decide on the right structure, often swapping out huge chunks of information, only to swap them back again half an hour later. …


Image for post
Image for post

Welcome back to the mini-series on Jenkins X. This section will be dedicated to setting up wildcard certificates and TLS for preview environments.

In my earlier post I discussed how to secure both:

  • the GKE cluster (using authorised network access and dedicated IP ranges for worker nodes, pods, and services)
  • the Jenkins X default services (adding ssl certificates and an IP whitelist for access)

That done, it was time to look at adding TLS to the dynamic preview environments Jenkins X provides.

Big thanks to Pablo Loschi at this point for his original Story on Using wildcard certificates with cert-manager…


Image for post
Image for post
Photo by Jose Fontano on Unsplash

Jenkins X is a great tool for quickly creating CI/CD pipelines on Kubernetes. However, the convenience of being able to set things so quickly also came with a couple of downsides. In a series of posts, I’ll discuss these and offer my take on how we solved some of them.

Before we start, I’d like to give a quick shout out to Ilya Shaisultanov, my counterpart across the water. Having colleagues like him make adventures such as these so much more enjoyable :-).

When creating the initial CI/CD infrastructure for Datameer, our big-data analytics company, we started out with the…

Steve Boardwell

Looking at all things Devops and Automation

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store