Jenkins-remoting-project

1. Project Overview

Jenkins Remoting is the subsystem that enables Jenkins to delegate build jobs to remote agent machines. Instead of running all builds on the master server, Jenkins distributes work across multiple nodes — each running independently and reporting results back to the master.

This project demonstrates setting up a fully distributed Jenkins build environment using Docker containers on a single Windows machine. Each Docker container simulates a real remote agent, making the setup equivalent to a real multi-machine CI/CD environment.

2. Objectives

Set up Jenkins Remoting to connect remote Jenkins nodes
Distribute build loads across different machines securely
Run jobs on various architectures remotely
Improve security using node isolation
Gain hands-on experience with Jenkins’ remote execution capabilities

3. Tools & Technologies

Tool	Version	Purpose
Jenkins	LTS (latest)	CI/CD master controller
Docker Desktop	Latest	Container runtime on Windows
Jenkins Remoting	Built-in	Agent-to-master communication protocol
JNLP / TCP	Built-in	Agent launch method
PowerShell	5.1+	Command-line interface on Windows
Docker Bridge Network	Built-in	Isolated network for containers

4. Architecture

┌─────────────────────────────────────────────────┐
│              Docker Network: jenkins             │
│                                                  │
│  ┌──────────────────┐                            │
│  │  Jenkins Master  │  ← Port 8080 (Web UI)      │
│  │   (controller)   │  ← Port 50000 (Agents)     │
│  └────────┬─────────┘                            │
│           │  Jenkins Remoting (TCP/JNLP)         │
│    ┌──────┴──────┐                               │
│    │             │                               │
│  ┌─┴──────┐  ┌──┴─────┐                         │
│  │ Agent 1│  │Agent 2 │                          │
│  │ linux  │  │ linux  │                          │
│  │(build) │  │(build) │                          │
│  └────────┘  └────────┘                          │
└─────────────────────────────────────────────────┘

How it works:

The Jenkins Master runs the web UI and schedules jobs
Agents connect to the master via the Jenkins Remoting protocol over TCP port 50000
When a job is triggered, the master delegates execution to an available agent based on labels
The agent runs the job, and streams results back to the master in real time

5. Phases of the Project

Phase 1 — Environment Setup
Phase 2 — Connect Remote Nodes