DevOptics Update – Dec 2018

The DevOptics team is hitting speed and we are cranking new features.  The CloudBees blog and the DevOptics ChangeLog are pretty good at tracking these changes but here is super-quick pass on some of the most recent changes.

Help now with ChangeLog and Support

We added links in the help icon to the DevOptics ChangeLog and, if the account is Standard or Starter-Kit to Support

Improved Modeling of Value Streams

The graphical value stream editor has been improved to help model Value Streams earlier in the development process.  The editor now allows the creation of new gates, new phases, connecting and deleting of gates and transitions, and, separate the mapping of these gates to jobs that are being instrumented.  By separating modeling from instrumentation, DevOptics now can be used easily to describe, reason about and improve the software delivery. 

Value Streams for Micro-Services

DevOptics now supports Value Streams that have multiple ending gates.  This corresponds to a software situation where there are multiple software pipelines, delivering multiple artifacts.  In the case of us, the DevOptics team, we have one software pipeline for each server-side (micro) services, and for our plugin.

Filters per Master in CD Platform Analytics

The CD Platform Analytics now supports filtering per master

Export Metrics to CSV

Metrics can be exports to CSV format for further processing or presentation

Group Tickets by Run

Previously tickets in a gate – shown in gate details – where sorted “chronologically”.  The precise date was that of the creation of the commit.  We now show the tickets grouped by the run that made them change gates. 

The new display is much more useful.  For example, in a deployment gate, the grouping shows what features were promoted in the last run, and that is what I, as an engineering manager, can use to track that activity

Produces / Consumes for Value Streams

There is a new mechanism for tracking the production and consumption in Gates.  We support scripted pipelines, withMaven steps, and Freestyle jobs.

Here are two examples from the section on pipeline steps of the documentation 

For more details check out the documentation:

And More…

I’m using the DevOptics tag for all the posts on that topic, so you can find them all HERE.

Join us! Looking for a RSE/OPS/Cloud Engineer for DevOptics

The DevOptics team has an opening for an OPS person to contribute to our architectural, operational and implementation activity as a modern SaaS.  We are a distributed team operating across multiple time-zones.  We are looking for somebody that will work in Eastern / Central US Time-Zone.

We interact continuously online, synchronously and asynchronously, we complement this with F2F meetings.  Below is a photo from our last F2F, in Malahide, IRL.

Our last F2F in Malahide

Job details HERE.  Looking forward to meet you!

PS.  We collectively speak (at least) 6 languages, have 8 nationalities, and live in 7 countries.  We value diversity although, as you can see from the photo, our efforts have not been fully successful.  Apply!

CloudBees DevOptics New Features (mid-Oct ’18)

This is an indirect link to the official post.

Our team has been delivering improvements to CloudBees DevOptics since DevOps World | Jenkins World 2018 in San Francisco.  Now, as we we head to DevOps World | Jenkins World in Nice, France, I want to point out how we use the continuous delivery model ourselves to improve and update our own products.


The rest of the post is HERE.

CloudBees DevOptics at DevOps World | Jenkins World 2018 (from CloudBees Blog)

This is an indirect link to the official post.

Last month I attended our annual DevOps World | Jenkins World 2018 in San Francisco. The event has gotten bigger every year, and – spoiler alert! – next year the conference will be at the San Francisco Moscone Center.

CloudBees DevOptics was an integral part of the event and this post will highlight new updates and features to the product. But first, I’ll give you a recap of what happened in San Francisco…

The rest of this HERE

Switching the Account for a Master

Connecting a Master – CloudBees or Jenkins – from DevOptics is very easy.  So it is to Disconnect and Reconnect with a new account.

A quick visual pass.  First disconnect your master.  You can do this here:


Click on that Disconnect… then confirm


And now your master is no longer connected


Now you can reconnect again, with your new organization


There, that’s it.


DevOps World | Jenkins World 2018

And it’s a wrap!

This year’s DevOps World | Jenkins World 2018 wrapped up yesterday.  It was a very good show.  Our team had released the Free version of DevOptics earlier, but we spent all last week polishing… and some of this week too – the beauty of a SaaS product.

The event is at the San Francisco Marriott Marquis, in the big rooms of the Yerba Buena level.  The event is larger every year:


The setup for the keynotes was very nice.  These media guys do an outstanding job.  Last year they had 2 Christie Boxer 4k30 (that is 4K pixels, 30K lumens, 2,000:1 contrast!), projectors combined to provide a (very large) screen resolution of 3640×1050.  This year they had 4 of these beasts: two were used for the two side screens and two more overlapped to deliver a very cute round center screen.  The 2 overlapping projectors are at the edges of the room and there is no shadow behind the speaker

Here is Christina in front of the rotating globe.  Very sharp looking.


Kohsuke gave his usual Community Keynote, and then Sacha and Christina presented.  DevOptics got a piece of the keynote:


The main announcement was CloudBees suite – we are at the top, over CloudBees CodeShip and CloudBees Core (based on Jenkins):


The trade show had nice attendance.  This year I was not running the DevOptics booth, at the back of the picture – which suited me well, I was busy keeping an eye on the actual system.


The product itself behaved very nicely.  No service interruptions (yeah!) and only a few new bugs.  We actually fixed several during the week — SaaS FTW.   I’ll write a follow-up post on that part of the show experience this weekend.

And next year the show goes to a bigger stage – the Moscone Center!

Connected Masters for Run Insights

Embracing a SaaS culture requires a fair amount of infrastructure and adjustments to the operations of the team but it enables great speed in delivering new product features.

Our team delivers new services multiple time a day.  Sometimes the features are small and sometimes they are invisible to the end-user, but here is a very useful one that we shipped late last week: we have expanding the screen that lists Connected Masters and it now lists all the connected Masters in your Organizations, with extra information.

This feature can be very useful when you are getting started with Run Insights;.  Once you have connected a new (Jenkins or CloudBees Core) Master using the DevOptics Plugin, first go to the Settings icon on the lower left, and then go to the Connected Masters screen to see that your Master connected as you expected.

Below is a screen showing some of the Masters in our own Organization.  I sorted the list and oranged-out all but the first Master.  You can see that the version of the plugin installed in this particular Master is 1.1349 – the versions are generated automatically and continuously – and that the plugin has been configured to provide Monitoring Information on the CD Platform, and Information on the Value Streams (see Configuring the DevOptics Plugin).


Recent promotions have also improved the in-app documentation, on-boarding,, and messaging around the plugin installation.  Go SaaS!

A Jenkins Run… seen from DevOptics

After Configuring and Connecting your DevOptics Plugin on your Jenkins installation, your DevOptics UI looks like this.


That is actually the Run Completion tab. The Run Insights screen has 2 other tabs, all equally empty.  Activity by hour of the Day is:


and Runs per Node Label looks as follows:


To see some activity you need to run some jobs in one of the masters connected to this account.  In our setup, that is our local master.  So… let’s run the simplest Hello World job.

Go to the Jenkins instance and look at that “New Item” on the left menu


From there, we can create the simplest FreeStyle job (yeah, you should do something cleaner, but I am running with no Plugins, so…)


Filling in the fields:


and now you can just run this job…


Let’s do it a few more times… and then let’s go to the DevOptics UI side… and this is how it will look


And a bit later…


so there you have it: your own Jenkins instance running a Hello World job, as seen by DevOptics in your Organization.  It takes a bit more than the ideal 5 minutes but it’s not too bad… I hope! 🙂

Enjoy DevOptics, and stay tuned for more developments and features…

And, collecting my most recent posts for your convenience:

Configuring the DevOptics Plugin

Once you have installed the DevOptics Plugin you need to configure it.  The plugin checks for multiple gotcha’s.  It also handles the case where you are only interested in the data needed for Run Insights, or also for Value Streams.  The Value Streams data needs additional plugins; that is explicitly handled by the plugin.   In this narration, I’ll show how to configure the plugin for Run Insights

Starting where Installing the DevOptics Plugin post ended, look for the DevOptics section of managing Jenkins:


And then run the Plugin.  The plugin is split in 3 sections.  The first section does configuration setup, the second section is on Run Insights and the last is for Value Stream Section.

Below is the screenshot showing the sections BUT don’t rush to it yet…


The one detail to take into consideration is that section where you are asked for the “instance URL”.  For technical reasons  – see this Community Question – you want a proper name for your Jenkins installation.  In my case, I configured my Mac in the Settings screen, under Sharing:


And then you can use that in your Jenkins configuration here:


Now, we can actually go through the DevOptics Plugin:

DO-20The plugin checks a bunch of things and will insert those check marks as it goes along.  In our case the first section passes well, and so does the second, on Run Insights.  The third section, on Value Streams, would require additional plugins to install.  We will skip that because we are not going to use it for now.

If you are following along with your own instance you will notice a small – but critical – difference between your instance and the above screenshot.  The screenshot above shows you connected as follows:


That’s because I had forgotten to take the screenshot the first go around (oops).  Fortunately, that “Reset” button works, so I can reset the connection and then that section looks as yours should look:


If we now connect via that button, we will activate the authentication into DevOptics – see the screens in my earlier Free DevOptics Run Insights post – and, after that, you get to:


This screen let’s you chooser which Organization (aka Account) to use, although in this case there is only one.  Choose the Account you want, then click Connect, and you have now connected your Plugin to your DevOptics Organization.

This takes much longer to type than to do; it should have taken you 5 minutes or so….

Next post will show how the SaaS UI looks like after all this.  And it will show the Jenkins-noob how to trigger a job and see the results on the UI.

Other posts on this topic include:

Installing the DevOptics Plugins

DevOptics runs on the standard (open source) Jenkins distribution.  You just need to install the plugin and configure it.  The only unusual bit is that you will need to install two plugins, one is the DevOptics Installer, and then, after installing that, the DevOptics Plugin itself (the first step is not needed if you are installing on a CloudBees distribution).

The whole experience, from starting the download to configuring the plugin should take less than 10 minutes.  Here is a step-by-step narration:

First go to the Jenkins installation page:


I’m on a Mac, so I choose the MacOS X installer; with my network connection it takes about 4 minutes


Now start the installer


Go through all the screens …


and you will soon reach Jenkins itself.  You need to create an account, etc….

You do not need to install all the recommended plugins; skip that and you will save yourself quite a bity of time (I need a screenshot of this step).


Now go to Manage Jenkins, to add the Plugins.  First look for “Available” plugins, searching for “DevOptics”.  You will find only one plugin, the “Installer”


Go install this.  You do NOT need to restart.


After this go again to the Plugin Manager.  Search again and you will find another DevOptics Plugin.  This is the real plugin that will collect the data needed by our DevOptics SaaS Service and App.


You can now install this Plugin; this is the real thing.  As before you do NOT need to restart.


And there you are!  The next step is configuring the plugin; I’ll go over that in the next post.

Other posts on this topic include: