One release pipeline for six backend services

Quality gates at every stage and a single release flow, so faulty builds stop before deployment.

My role Defined the backend QA strategy; designed and rolled out the pipeline

Context

Six backend services at TradingView, each moving from commit to production. The goal was one consistent path to release, with quality checks that nobody can skip.

Strategy

Put a gate at every stage — lint, unit, coverage, deploy, integration, end-to-end — so a faulty build is blocked as early as possible, and give all services the same release flow.

What I did

Implemented CI/CD quality gates for 6 services: lint, unit, coverage, deploy, integration and E2E.
Designed a unified GitLab CI release pipeline with one-click versioned release branches.
Automated staging deploys with integration and E2E gates.
Added a Slack-threaded release audit trail and change-managed production deploys through ITSM.
Developed 4 and maintained 13 Jenkins build and check plans.

Results

Metric	Before	After
Services behind quality gates	—	6
Cutting a release branch	—	One click
Release audit trail	—	Every release, in Slack

Stack

GitLab CI
Jenkins
Docker
Kubernetes
Slack
ITSM