How jhonatademuner/release-guard works
Project type and purpose
• This is a backend-only, Kotlin-based Spring Boot microservice (“Release Guard”) whose role is to validate Jira issues (and optionally GitHub PRs) for release readiness. It exposes REST endpoints for CI/CD pipelines, integrates with external Jira and GitHub APIs, applies block-schedule rules (from a JSON file), and returns simplified domain objects or block statuses.
File structure
• Top-level build & config: Dockerfile, Gradle scripts, application.properties, logback.xml.
• src/main/kotlin/com/releaseguard:
• controller/… → REST API entry points (GithubController, JiraController, MergeController, BlockScheduleController)
• service/… → business logic (GithubService, JiraService, MergeService, BlockScheduleService)
• client/… → outbound adapters (JiraClient, GitHubClient)
• domain/… → strongly-typed models for Jira, GitHub, schedule
• utils/ → assemblers (map raw DTOs → domain), exception handlers, filters
• config/ → RestTemplateConfig, request logging filter
• data/block-schedule.json → rule definitions for schedule checking
• test/… mirrors main code for unit & integration tests
README for additional insights
• REST endpoints: /api/jira/issue/{key}, /api/jira/issue/{key}/block-status
• Key features: simplified issue info, block-status check, CI/CD integration, custom exception handling
• Tech stack: Kotlin, Spring Boot, Gradle, RestTemplate, Jackson, JUnit5, MockK
Detail without over-fragmenting
• Controller & corresponding service
• File block-schedule.json feeding into BlockScheduleService