Sitemap

Member-only story

๐“๐ก๐ž ๐ƒ๐ž๐Ÿ๐š๐ฎ๐ฅ๐ญ ๐๐จ๐ซ๐ญ๐ฌ ๐„๐ฏ๐ž๐ซ๐ฒ ๐ƒ๐ž๐ฏ๐Ž๐ฉ๐ฌ ๐„๐ง๐ ๐ข๐ง๐ž๐ž๐ซ ๐’๐ก๐จ๐ฎ๐ฅ๐ ๐Š๐ง๐จ๐ฐ (๐€๐ง๐ ๐–๐ก๐ฒ ๐“๐ก๐ž๐ฒ ๐Œ๐š๐ญ๐ญ๐ž๐ซ)

4 min readOct 15, 2025

--

Press enter or click to view image in full size

A few months ago, our team faced a weird production issue.
A Jenkins pipeline failed to deploy, and everything looked fine โ€” code, credentials, permissions.
After hours of digging, we discovered the root cause: port conflict.

Someone had launched a small testing service that accidentally occupied 8080, Jenkinsโ€™ default port.
The entire deployment chain was stuck because of one small oversight.

That night reminded me of one simple truth โ€”

Every DevOps engineer should know the default ports of the tools they use daily.

So today, letโ€™s revisit those basics. Not as a list of numbers to memorize, but as a DevOps survival guide โ€” the ports that keep our automation, pipelines, and monitoring alive.

Jenkins (8080)

Function: Jenkins automates our CI/CD pipelines for building, testing, and deploying code.
Itโ€™s the backbone of continuous integration and continuous delivery.

Default Port: 8080

--

--

Bharath Kumar Reddy N.
Bharath Kumar Reddy N.

Written by Bharath Kumar Reddy N.

"Senior DevSecOps Engineer with 10+years of experience streamlining development cycles and enhancing collaboration between development and operations.