Tested release pipeline
A containerized web app that could only reach users after its tests passed, with a separate QA environment updated first.
Code & evidenceWhat I built
- GitHub Actions ran unit, integration and real-browser tests on two processor types before building and publishing each Docker image.
- Pushing to the QA branch updated a QA site automatically; merging into main updated production. Production stayed unchanged until that merge.
- The workflow then checked over HTTPS that the expected commit was actually running.
- The server only allows SSH-key logins for a non-root account; root and password logins are refused.
Why it matters for game teams
Game studios ship builds constantly. The same idea, where nothing reaches players until the checks pass, is the core of build and release engineering.
Evidence
- Recorded test runs, deployed commits and screenshots (observed October 15, 2026)
- GitHub Actions history
Note: the original demo sites at xenoshin.com and qa.xenoshin.com were retired in November 2026, after the project was graded, to make room on the server for this portfolio and the Elestrals app. The recorded evidence above is unchanged. The pipeline idea lives on: this site's own tests must pass before the server updates.