CI/CD
The problem
A home equity operation goes through many hands (partner, analysis, legal, payment) and every stage requires documents and checks. Without a single place, operations stalled and nobody knew which stage they were in or what was missing to move on.
On every PR: the changelog runs on an empty database and is rolled back, each service runs its tests at 100% coverage in parallel and the front-ends pass lint, typecheck and build. Deploy is manual: images to ECR, migration first, then the rollout.
Decisions and why
- One matrix job per service
- Seven services test in parallel and one does not hide another's failure (fail-fast off).
- Migration before rollout
- New code only gets traffic once the schema is ready.
- Deploy on a button
- Releasing is a decision, not a side effect of a merge.
requestresponse
Pick a scenario above to watch the message travel through the architecture.
What it looks like
Replica of the pipeline board with fictional data (internal system) esteira.evilrabbit.com.br/lines/triage
Triagem
Conferência de dados2
Marina SouzaGMR$ 480 mil 1 d
Paulo HenriqueR$ 1,2 mi hoje
Combate à fraude1
Ricardo AlvesAPR$ 750 mil 4 d
Validação dos documentos2
Carla PradoGMR$ 610 mil 2 6 d
João ReisR$ 295 mil 2 d
Aguardando aprovação0
Nada aqui