Loading…
22
A junior dev asked why I scan containers after deploy instead of before, and I didn't have a good answer
I was doing a code review on Tuesday when a guy on my team with about 8 months of experience asked why we run the image scan in the pipeline after the deploy step instead of before it. I started explaining the old setup and halfway through I heard myself and realized the reason was just that nobody had moved it. We flipped it in about 20 minutes in the Jenkinsfile and caught a broken base image the next morning before it ever got near staging. Guess I had been treating a workaround like it was a real choice for way too long. Anyone else have a pipeline step that only exists because nobody questioned it?
0 comments
Log in to join the discussion
Log In0 Comments
No comments yet
Be the first to share your thoughts on this discussion.