Inspiration
Shipping code is not the same as proving that a release is ready. Automated pipelines generate useful evidence, but release decisions can still be difficult to understand, audit, and reproduce.
Release Guardian was created to make that evidence easier to inspect and turn it into clear release-readiness decisions.
What it does
Release Guardian is a CI-based release evidence gate that organizes testing, security, build, and verification results into auditable release decisions: GO, HOLD, or BLOCK.
The project focuses on traceability, visible pipeline execution, and explicit conditions rather than assuming that a successful build automatically means a safe release.
How we built it
The project was developed in a GitLab hackathon repository using a dedicated feature/release-guardian branch and Merge Request !1.
Its GitLab CI/CD pipeline includes four stages: testing, security, build, and verification. The project keeps its source changes and pipeline history available for inspection.
Challenges
The main challenge was separating the existence of automation from proof that the automation actually ran. Another challenge was expressing release-readiness decisions using reproducible evidence rather than unsupported assumptions.
What we learned
A trustworthy release workflow needs transparent checks, visible evidence, and clearly defined failure conditions. GitLab merge requests and CI/CD provide a useful foundation for this approach.
What's next
The next step is to validate the complete agent-assisted workflow with GitLab Duo Agent Platform and demonstrate the actual execution, including what the agent does and where human approval is required.
Built With
- agent
- ci/cd
- duo
- gitlab
Log in or sign up for Devpost to join the conversation.