Repository navigation
fix(docker): add --self-test startup check to fail image build on unloadable base - #447
Conversation
Roslyn analyzer findings
|
Add a --self-test switch to BuildBot that starts the server and checks it responds, and run it as a RUN step in the Dockerfile so a broken image fails at build time. Refs #445
|
Development: implemented |
|
Simplify clean - advancing to code review |
|
Code review clean - advancing to security review |
|
Code review clean - advancing to security review (board moved by the orchestrator: the session reported no findings but did not move it) |
|
Security review clean, advancing to coverage check |
|
.NET 94.4% < main 100.0% - returning to Development Uncovered: BuildBot 118/190 lines (62.1%); all other projects 100%. Needs tests for the new |
Add tests for the self-test startup path: application config locator, server startup, program entry, and a shared test config folder helper. Move self-test startup logic out of SelfTestTests into ServerStartup and ApplicationConfigLocator.
|
Development: Fixed in 6d12275: added tests covering the |
|
Simplify clean - advancing to code review |
|
Code review clean - advancing to security review |
|
Security review clean, advancing to coverage check |
|
Coverage ratchet passed - advancing to Human Review (.NET 100.0% >= main 100.0%; COVERAGE.md updated in 1c85102) |
AI Review Loop: reviewed 1c85102 |
Super-linter summary
All files and directories linted successfully For more information, see the GitHub Actions workflow run Powered by Super-linter |
Adds a
--self-testmode to BuildBot (Program/SelfTest/ServerStartup) and a DockerfileRUN ["/usr/src/app/BuildBot", "--self-test"]step so an image whose runtime cannot load the application fails at build time rather than at start-up. Includes tests (100% line coverage) and updated COVERAGE.md.Closes #445