Operations Center Docker Demonstration

Article ID:203802590
2 minute readKnowledge base

We have set up a Docker image so that users can quickly try out CloudBees Jenkins Operations Center by CloudBees.

The demo sets up the following:

  • CloudBees Jenkins Operations Center Master

  • Client controller in a highly available mode with a backup master

  • Shared Agents

  • Agents local to client controller

  • Folders/Folders plus: ties agents to a particular folder

  • Templates

  • RBAC

  • RBAC with a secret project

Follow the excellent tutorial, if you like to set Jockey up yourself


Run docker on your machine, if you are on mac - you will have to edit /etc/hosts to add the DOCKER_HOST IP address and map it to jockey.local.


Now run the docker image

docker run -p 80:80 -it -h jockey.local cloudbees/joc-trial

Navigate to http://jockey.local/operations-center, accept the license on the license screen and log into Jockey u/p: admin/admin (or harpreet/harpreet).


Jockey server automatically grants license to individual controllers but to get this place in the demo, we need to explicitly connect a client controller to Jockey server.

Click on Jenkins-a (which is the client controller in the demo)


Click “Release” link.


Click the “Release” button. This will take you to a screen that shows the “connection details” for connecting to the client controller - make sure you copy this you will need it in the next step.


Demo jobs and configurations

Navigate to http://jockey.local/jenkins-a. You will be presented with a license screen, choose the “I have connection details for a CloudBees Jenkins Operations Center server that will issue my license key” and paste the connection details from the previous step.


Once done, you can click on “jenkins-a” and navigate to the Jenkins client controller. There are numerous jobs and folders that demo individual features:

  1. backup-hourly-shared-slave: shows a backup job using the backup plugin that uses shared agents setup on Jockey server.

  2. gasp-server-on-slave-from-operations-center: a maven job using a shared agent

  3. secret-project: you can view this folder either as an admin or as stephen (u/p stephen/stephen). If using other logins, you cannot view the folder.

  4. slave-per-folder-and-templates: demos the folders plus and templates feature from CloudBees Jenkins Enterprise.


Secret project

Navigate to the secret-project folder and click on “Groups” to see how the permissions are setup. In this case, we have added a secret-group with stephen as the only member here. If you navigate to roles, you will see that we have filtered out developer and browser roles.


Slave-per-folder and Templates


Monitoring on CloudBees Jenkins Operations Center Dashboard


Global Security Configuration

We have used mock-security-realm plugin for authentication. The first entry is user name and password and the second entry mimics an external group. For e.g: “admin admin-ext” translates to a u/p of admin/admin and admin belongs to an external group called “admin-ext”