4 ms·

If you don't publish your build artifacts, what are you deploying?

• GauntletWizard 5y ago
  An incredible amount of companies have a "release" build pipeline; They don't simply release some sufficiently tested version of master, but cut a branch and muck with things until they get a "release". This is the source of many, many bugs in software that is shipped, and many many regressions as "release" branches are reused inappropriately.
  • deckard1 5y ago
    oof. I've been there. One day my manager asked me if I could cherry-pick a large amount of code from master into their Frankenstein "release" branch. I thought about it for a minute trying to figure out a polite way to say "you all are fucking insane, you know?" before settling on "okay, I can do that but if this breaks it's on you." I'm pretty sure if you have releases and they involve half a dozen "hot fixes" then you're doing CI/CD wrong. But what do I know. Everyone is still drinking that agile kool-aid.