Loading…
15
Our Jenkins builds went from 22 minutes down to 8 after one change to the SAST step
Six weeks back our scan step was running on every single commit and the devs were losing their minds waiting on feedback. I moved it to run only on pull requests and the main branch merges, then added a 90 second timeout with a fail-fast flag. Build time dropped from 22 minutes to 8 the same day. Same tool, same rules, just a scheduling change. Anyone here run scans on a schedule instead of per commit, or does your team want that gate right at the commit?
1 comments
Log in to join the discussion
Log In1 Comment
anna56710d ago
Ever wonder if the per commit gate is actually worth it? A buddy of mine had the same mess, his team swore they needed scans on every push until they tried batching them on PRs, and nobody missed the old way. Funny how fast people change their minds once the waiting stops.
8