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:
The 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:
- Announcing Free DevOptics Run Insights
- Installing the DevOptics Plugin
- Configuring the DevOptics Plugin, and
- A Jenkins Run… Seen from DevOptics