KamoCRM

Fail the image build when a bean has ambiguous constructors or a clashing name — the five-crash-loop chain after 8f05537 (Meet Stage MS5 follow-up)

BuildMediaService
Shipped
November 17, 2026 at 3:29 AM UTC
Author
Kamo
Commit
d957fa5

BeanWiringRatchetTest scans com.kamo with Spring's own scanner and bean-name generator: a stereotype class with >=2 constructors, none @Autowired and no no-arg one, or two beans (components or @Bean methods) sharing a name, fails. CI skips tests, so the Dockerfile compiles and runs just this guard (~10 s) against the packaged classes. Mirrors SecurityService's ****************

All changes

Like what you see shipping?

All of it arrives in your workspace on its own. Start on the free plan and read this page again in a month.

Start Free ForeverView Pricing