267
Let's blame the dev who pressed "Deploy" (yieldcode.blog)
submitted 2 years ago by to c/technology@lemmy.world
68 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 14 points 2 years ago (2 children)

Was there a process in place to prevent the deployment that caused this?

No: blame the higher up

Yes: blame the dev that didn’t follow process

Of course there are other intricacies, like if they did follow a process and perform testing, and this still occurred, but in general…

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 23 points 2 years ago (1 child)

    How could one Dev commit to prod without other Devs reviewing the MR? IF you're not protecting your prod branch that's a cultural issue. I don't know where you've worked in the past, or where you're working now, but once it's N+1 engineers in a code base there needs to be code reviews.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [+] -10 points 2 years ago (2 children)

    Oh you sweet summer child...

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 11 points 2 years ago

    I hate to break it to you, but companies with actual safe rails to deploying to production do exist.

    And when things go wrong, it's never the responsibility on a single dev. It's also the dev who reviewed the PR. It's also the dev who buddy approved the deploy. It's the whole department that didn't have enough coverage in CI.

  • permalink
  • fedilink
  • source
  • parent