KalpOps Evolving Eternally
"Recall the face of the poorest and weakest person you have seen, and ask if the step you contemplate is going to be of any use to them." — Mahatma Gandhi

Authenticating...

Access Denied

Your account has been blocked from accessing this site.

If you believe this is an error, please contact the site administrator.

← Back to Portfolio
DevOps

Jenkins Pipeline Optimization & Modularization

Refactored a complex, monolithic 500+ line Jenkinsfile into a clean, modular architecture with 3 focused jobs, external tool scripts, and parameterized execution – enabling faster builds and local pre-commit checks.

JenkinsGroovyBashSonarQubeGradleGit

🔥 The Problem: Monolithic Pipeline Complexity

The original Jenkinsfile had grown into a 500+ line monolith with 10+ stages, embedded functions, and tightly coupled logic – making it slow, hard to maintain, and impossible to test locally.

10+ Pipeline Stages
500+ Lines of Groovy
25+ Min Build Time
0 Local Testability
⏱️ Long feedback loops – devs wait 25+ mins for simple checks
🔒 No local validation – must push to trigger pipeline
🧩 Everything coupled – can't run checks without full build
📄 Hard to debug – embedded functions, no separation

🚀 The Solution: Modular 3-Job Architecture

I redesigned the pipeline around separation of concerns, splitting the monolith into three focused jobs with external tooling that developers can run locally.

New Architecture
✅
CHECK
Validation & Static Analysis
Runs Locally
→
🔨
BUILD
Compile & Package
→
🧪
TEST
Unit Tests & Quality Gates

🔄 Key Architectural Changes

1 Stage Consolidation
Before: 10+ stages (SQL checks, Binary checks, Password checks, JIRA validation, PR detection, Compile, Tests, Sonar...)
After: 3-4 stages per job (Check, Build, Test, Quality Gate)
2 External Tool Scripts
Before: All logic embedded in Jenkinsfile as @NonCPS functions
After: /tools directory with standalone scripts called from pipeline
3 Local Execution
Before: Must push code to trigger any validation
After: ./tools/check.sh runs all checks locally before commit
4 Parameterized Control
Before: Fixed behavior, no developer override
After: Flags like --skip-sql, --only-java, --fast-mode

📂 The /tools Directory Structure

Scripts moved out of the Jenkinsfile into standalone, testable utilities:

📜
check-sql.sh Validates SQL files are in correct paths, DDL/DML naming, PL/SQL duplication
📜
check-binaries.sh Blocks .war, .jar, .tar, .gz, .zip files from being committed
📜
check-secrets.sh Scans property files for encrypted passwords (AES, 3DES)
📜
check-jira.sh Validates PR title contains valid JIRA ID format
📜
detect-changes.sh Identifies affected modules for selective compilation
🚀
check.sh Master script – runs all checks with optional flags

⚙️ Parameterized Execution Flags

Both the pipeline and local scripts now accept flags for granular control:

--skip-sql Skip SQL validation checks
--skip-binaries Skip binary file detection
--only-java Only compile Java, skip JSP
--only-jsp Only compile JSP files
--skip-tests Skip unit test execution
--skip-sonar Skip SonarQube analysis
--fast-mode Minimal checks for quick iteration
--modules=X,Y Build only specific modules

🏆 Results Achieved

Before

  • 25+ minute full pipeline
  • No local validation
  • 10+ tightly coupled stages
  • 500+ lines in Jenkinsfile
  • Hard to debug failures
  • No selective execution
→

After

  • ~8 minute optimized builds
  • Local pre-commit checks
  • 3 focused, independent jobs
  • ~100 lines per Jenkinsfile
  • Clear, isolated failures
  • Parameterized control
70% Faster Builds
5x Smaller Jenkinsfiles
100% Local Testability
∞ Developer Happiness

Session Timeout Warning

You've been inactive. Your session will expire in 60 seconds.