Distributed SCM Consolidation and CI/CD Standardization

Consolidated source control scattered across SVN, a self-hosted GitLab, and local build environments onto a single GitLab platform, and built the company-wide CI/CD system from the ground up. Designed a standard template system per OS (Linux/Windows), build system (Java/C), and deployment method (SSH/Kubernetes/Docker) combinations. Containerized Java projects by JDK version. Defined phased rollout scope for C projects based on server dependency analysis.

Architecture

InfoGrab Finance

2025.06 - 2025.11

S Payment

Tech Stack

GitLab CI/CD Docker Kaniko Prometheus Nexus

Highlights

Single-GitLab SCM consolidation + company-wide CI/CD built from scratch
Standard template system per OS/build/deploy combinations
Java JDK version-specific Dockerfiles with Kaniko-based container builds
C projects: phased migration scope based on server dependency analysis

Key Tasks

SCM Consolidation

Analysis of SVN, self-hosted GitLab, local build environments
Single Omnibus GitLab platform setup
History-preserving migration execution
Branch strategy standardization (GitFlow-based)

CI/CD Standard Template System

Templates per OS(Linux/Windows) x Build(Java/C) x Deploy(SSH/K8s/Docker)
Java version-specific build templates (Java 8/11/17/21)
Include-based centrally managed template structure
Enterprise-wide deployment

Build Environment Containerization

Java projects: JDK version-specific Dockerfiles and containerization
Kaniko-based image build pipeline setup
C projects: excluded from containerization due to server dependencies, designed parameter-based execution
Phased migration scope based on technical constraints

Monitoring System

Prometheus-based GitLab infrastructure monitoring
CI/CD pipeline performance metrics collection
Alert rules and dashboard configuration

Operations Team Training

GitLab operations guide documentation
CI/CD template usage training
Operations team self-management capability

삶을 기록하는 두 축

Architecture