relmgr-web

relmgr-web is a microservice-based web application designed to automate and standardize release-related workflows such as patch packaging, artifact publishing, and release notifications. The project is a web evolution of the desktop prototype relmgr.

What relmgr-web does

The application supports several release-oriented workflows:

• Application patch preparation
  • Generate release emails and chat messages
  • Standardize notification templates
• Patch release automation
  • Analyze base versions
  • Prepare ZIP artifacts
  • Upload artifacts to Nexus
• Patch by task
  • Generate patch packages based on task lists
  • Produce release messages for chat systems

Each workflow is represented as a dedicated UI flow and backed by a separate service or module.

Project Goals

The main goal of relmgr-web is to reduce manual effort and human errors in release engineering workflows by providing:

• A unified web UI for release-related operations
• Reproducible and transparent release steps
• Automated generation of artifacts and notifications
• Clear separation of responsibilities via microservices

This project is built as a portfolio-quality system, demonstrating architecture, frontend–backend integration, and real-world automation scenarios.

Architecture overview

The system follows a microservice-oriented architecture:

• React frontend communicates with backend services via REST APIs
• Spring Cloud Gateway acts as a single entry point
• Backend services are organized as independent Gradle modules
• Cross-cutting concerns (routing, CORS, aggregation) are handled at the gateway level

Relationship to Desktop Version

The original relmgr desktop application was implemented as a JavaFX-based prototype focused on local automation.

relmgr-web:

• Re-thinks the same domain in a distributed, web-based architecture
• Focuses on microservices, APIs, and modern frontend
• Is intended as a scalable foundation rather than a local tool

Some screenshots

Application patch — Email & Chat generation

Patch by task — Zip & Message generation

Patch release — Patch analysis & Nexus upload

Project status

Active development.

Current focus:

• Frontend feature completion
• Backend API integration
• Chat and notification delivery via external systems

Future steps include containerization and deployment orchestration.

Key technologies

• Frontend: React + Vite
• Backend: Java 21, Spring Boot
• Gateway: Spring Cloud Gateway
• Build system: Gradle (multi-module)
• API style: REST