NJCI/CD
PRODUCTION ONLINE

JENKINS DELIVERY INFRASTRUCTURE

Code enters.
Production emerges.

A two-node AWS delivery system engineered for repeatable releases, secure transport and automatic verification.

Initialize simulation ↗Inspect system →
LAST DEPLOYMENT#--SYNCINGAwaiting build-info.json
JJENKINS
GHSource
NProduction
awsCloud
DEPLOYMENT REACTORACTIVE
01

SYSTEM TOPOLOGY

A release path with
no invisible steps.

01 / SOURCEREADY
GH

GitHub Repository

Versioned application source and declarative pipeline configuration.

mainHTTPSSCM
SCM POLL
02 / ORCHESTRATEACTIVE
J

Jenkins Controller

Checks out, validates, packages and transfers the approved release.

:8080UBUNTUEC2
SSH + RSYNC
03 / SERVEHEALTHY
N

Nginx Production

Receives immutable website assets and serves the current release.

:80HTTPEC2
◇
Private VPC transport

Deployments use the target server's private address.

⌁
Key authentication

No password is stored inside the pipeline.

◉
Automated verification

HTTP validation closes every release.

↺
Versioned recovery

Git tags preserve previous releases.

02

END-TO-END WORKFLOW

From source change
to production traffic.

aws
AWS CLOUDVPC · AP-SOUTH-1
01
DEV

Developer

Changes website files and pushes a commit.

GIT PUSH
HTTPS
02
GH

GitHub

Stores source code and the Jenkinsfile.

MAIN BRANCH
WEBHOOK / POLL
03
EC2 · UBUNTU
J

Jenkins Server

Checks out, validates and builds deployment metadata.

PORT 8080
SSH + RSYNC
04
EC2 · UBUNTU
N

Nginx Web Server

Receives the release in /var/www/html.

PORT 80
HTTP
05
UI

Users

Open the public IP and receive the latest website.

PRODUCTION
External sourceAWS EC2 instanceAutomated data flowSecurity groups allow 8080 for Jenkins, 22 between servers and 80 for users.
03

LIVE DEPLOYMENT DATA

Real metadata.
Zero exposed credentials.

CURRENT RELEASE
#--

Loading deployment state

COMMIT-------Git revision deployed
BRANCHmainProduction source
DEPLOYED AT--:--Awaiting pipeline
WEB HEALTHHTTP 200Nginx response
RELEASE EVENTSLIVE FEED
04

PIPELINE SIMULATOR

Trigger a virtual
production release.

SYSTEM READY
01
⌘

Checkout

Fetch main from GitHub

STANDBY
02
✓

Validate

Inspect required assets

STANDBY
03
⇧

Deploy

Rsync over private SSH

STANDBY
04
◎

Verify

Confirm HTTP response

STANDBY
nexus@jenkins:~$

Pipeline engine waiting for input.

05

ENGINEERING STACK

Purpose-built tools.
One delivery system.

01
aws

AWS EC2

Isolated compute nodes

INFRASTRUCTURE
02
J

Jenkins

Pipeline orchestration

AUTOMATION
03
GH

GitHub

Versioned source control

COLLABORATION
04
N

Nginx

Production web serving

RUNTIME
05
>_

SSH + rsync

Secure asset transport

DELIVERY