> Jenkins specifically has no business being anywhere near a production deployment I'm curious about this -- what's wrong with using the same deployment tool f

> Jenkins specifically has no business being anywhere near a production deployment I'm curious about this -- what's wrong with using the same deployment tool for running dev _and_ the other environments? Jenkins itself is a life-saver for, like you said, doing development builds/testing/reporting, but if we've got one script that deploys an image to production, why not trigger it with a Jenkins job, if only to keep everything centralized and maintain coherent deployment histories?