Remoting Kafka

Build Status Join the chat at

This plugin can be found in Jenkins Plugin.


Slides for DevOps World | Jenkins World 2018 presentation available here.


Current versions of Jenkins Remoting are based on the TCP protocol. If it fails, the agent connection and the build fails as well. There are also issues with traffic prioritization and multi-agent communications, which impact Jenkins stability and scalability.

This project aims an update of Remoting and Jenkins in order to add support of a popular message queue/bus technology (Kafka) as a fault-tolerant communication layer in Jenkins.

More information about this project can be found at:

Release Notes


Developer documentation

How to run demo of the plugin

Using Docker

  1. Requirements: docker, docker-compose installed.

  2. Set environment variable DOCKERHOST

  • Windows: set DOCKERHOST=host.docker.internal
  • macOS: export DOCKERHOST=host.docker.internal
  • Linux: export DOCKERHOST=$(ifconfig docker0 | grep 'inet addr:' | cut -d: -f2 | awk '{ print $1}')
  1. Build the demo: make all.

  2. Run the demo: make run (without security feature make run-no-auth).

  3. Features in the demo:

  • Docker Compose starts preconfigured Master and agent instance, they connect automatically using Kafka launcher.
  • Kafka is secured and encrypted with SSL.
  • There few demo jobs in the instance so that a user can launch a job on the agent.
  • Kakfa Manager supported in localhost:9000 to support monitoring of Kafka cluster.
  1. Stop the demo: make clean.

Using Kubernetes

  1. Requirements: A Kubernetes cluster (e.g. minikube), Helm 2

  2. Run the demo:

helm dep build helm/jenkins-remoting-kafka && \
  helm install helm/jenkins-remoting-kafka -n demo -f demo/helm/values-override.yaml
  1. Stop the demo:
helm delete --purge demo