WWNIT SOLUTIONS
RUEN

Hi! I'm Ivan.

I build services and automate processes. I help with infrastructure, launch and ongoing support.

Solutions

Service development, infrastructure and automation for a specific challenge.

Cases

Real challenges, the solutions and the project outcomes.

Process

From the first conversation to launch and support.

Journal

Engineering notes and articles from practice.

Research

Technical studies, experiments and scientific publications.

Resume

Work experience, skills and a PDF resume.

Have a project in mind?

Get in touch through Telegram or email.

WWNIT Solutions
RUEN

Cases

Back
WWN
IT SOLUTIONSPROJECT FILE04 / 05

DEVELOPMENT & DELIVERY

A shared release process for different applications

Shared build, analysis and deployment workflows, so onboarding a project does not mean setting up the entire process again.

01

Challenge

Each new service needed separate setup

Teams used different technology stacks and deployment methods. Without shared rules, onboarding a project meant working out build, analysis and operations settings again. Repeated setup took time away from development.

02

Solution

Shared release workflows and automated project integration

Python, .NET and Node.js projects use shared pipelines, deployment standards and documentation. Code analysis is integrated into the development process, with automated project synchronisation.

03

In practice

New projects join a familiar process

Language-specific settings are accommodated while the release process stays consistent. Teams do not have to build a separate procedure for every service.

  1. The project joins the prepared build, analysis and deployment workflow.

  2. A change goes through build and code analysis; project synchronisation with the analysis system is automated.

  3. The application is deployed using shared standards; logs and monitoring support investigations after release.

Technical diagram and tools
Technical diagramLOGICAL CONNECTIONS

→ action or data flow · — functional relationship. Repeated blocks refer to the same component.

Code and build

  1. Python · .NET · Node.jsTeam projects
    Build
  2. GitLab CI · JenkinsShared pipelines

Quality analysis

  1. GitLab CI · JenkinsShared pipelines
    Analysis
  2. SonarQubeCode analysis
    Analysis result
  3. GitLab CI · JenkinsShared pipelines

Deployment

  1. GitLab CI · JenkinsShared pipelines
    Deploy
  2. HelmDeployment standards
    Application resources
  3. KubernetesApplication environments

After deployment

  1. KubernetesApplication environments
    Metrics and logs
  2. Logs & monitoringShared tools

SonarQube returns analysis results to the pipeline. CI/CD manages deployment through Helm.

Python · .NET · Node.js
Team projects
GitLab CI · Jenkins
Shared pipelines
SonarQube
Quality and synchronization
Helm
Deployment standards
Kubernetes
Application environments
Logs & monitoring
Shared tools

GitLab CI · Jenkins · Helm · SonarQube

04

Outcome

Three technology stacks, one approach to releases

Build and deployment processes were unified for Python, .NET and Node.js. Manual project synchronisation with code analysis was eliminated. Launching services requires less repeated setup and administration.

  • Shared pipelines and deployment standards.
  • Automated project synchronisation with code analysis.
  • Shared logging and monitoring after release.