Set up continuous integration

The build server must run every commit and block merges that break the Windows and Linux release builds. Add a CI pipeline that boots a clean Ubuntu 22.04 and a Windows Server 2019 agent, restores our Conan packages, builds Release and Debug with -O2 and AddressSanitizer respectively, runs unit tests, and produces artifacts named mygame-win.zip and mygame-linux.tar.gz. Wire notifications to dev-team@studio.com and require the pipeline to finish within 30 minutes.

Before I hand this CI to QA, make approval easy: show the expected build time up front, surface the failed-test count and stack trace summary, highlight external package installs and network calls that could flake, and flag any tests that require GPU or proprietary drivers. Rearrange steps so a quick smoke build can run in under 10 minutes for fast feedback.

I just pushed a change and the Windows Release build failed after linking; Linux passed. The commits touched shader compilation and a third-party physics library update. I'm worried a changed linker flag or the physics library binary is incompatible. I can't reproduce the Windows agent locally. What's the most likely cause and the next diagnostic steps I should run so I can get the pipeline unblocked?

Over the last three months our merges stall for hours because builds fail unpredictably and agents diverge. We waste time chasing environment drift and re-running flaky tests. Which three practical habits should I change in how we manage CI, build artifacts, and tests so build times shrink, flakiness drops, and reviewers stop losing patience?