CI/CD for Endur: releasing the database and JVS together
The thing you tested in UAT is byte-for-byte the thing that lands in production.
CI/CD for database and JVS
Endur releases fail in the gap between the code and the database. I build Azure DevOps and Octopus Deploy pipelines that version and ship database, interfaces, ATC and JVS as one artefact, with a rehearsed rollback.
The thing you tested in UAT is byte-for-byte the thing that lands in production.
Each one covers a single problem and how to fix it. Free to read, written by someone who still does the work.
Subscribe by email No sales emails. Unsubscribe any time.