The build was failing. Again.
Except, of course, the ghost in the pipeline—but that one, they had tamed long ago. mssqllocaldb
# In the pipeline's "Initialize" step & "C:\Program Files\Microsoft SQL Server\130\Tools\Binn\SqlLocalDB.exe" create "CodeCraftBuild" -s & "SqlLocalDB.exe" info "CodeCraftBuild" The output was magical: Name: CodeCraftBuild Version: 13.0.4001.0 Shared name: Owner: DESKTOP-BUILD-42\jenkins Auto-create: Yes State: Running Last start time: 10:34:22 AM Instance pipe name: np:\.\pipe\LOCALDB#F365A2E6\tsql\query The build was failing
“What’s that?”
Lena’s hands trembled as she typed:
“You can attach a debugger to the same process that’s running the database engine. When a test fails, you can pause both your app code and the SQL execution at the exact same clock cycle. Try doing that with a container.” The build was failing. Again. Except