Loading request...
Users are frustrated with long CI/CD waiting times, often taking 8 minutes or more for feedback. They suggest building tooling that runs pipelines locally in real time to provide immediate feedback instead of waiting for the full pipeline to complete.
Genuinely curious how yall deal with the CI/CD waiting game. My workflow right now: push a commit, wait 8 minutes for the pipeline, its red because of a flaky test or some YAML indentation thing, fix it, push again, wait another 8 minutes. Rinse and repeat 4-5 times on a bad day. Thats like 40 minutes of just... staring at a spinner. And thats before you factor in the context switching. By the time the build finishes I've already moved on to somethign else and now I gotta context switch back. I've been experimenting with running CI checks locally before pushing. Catches like 80% of the stupid stuff. Also started building some tooling that basically watches your repo and runs the pipeline locally in real time so you get feedback in seconds instead of minutes. Anyone else building workarounds for this? Or do you just accept the 8 minute tax as the cost of doing business?