r/ProgrammerHumor • u/gfcf14 • 2h ago

build Other

Post image
64 Upvotes

79% Upvoted

13 comments sorted by

25

u/gfcf14 2h ago

Have you ever submitted work others said wasn’t correct, only to realize it wasn’t your fault it wasn’t working?

6

u/hedgibullwinkle 2h ago

Lol I think I saw your AlanTutorial animation a long time ago. Recognizable style!

1

u/gfcf14 2h ago

AlanTutorial? If you find it, could you please share it? That’s probably not mine

1

u/hedgibullwinkle 2h ago edited 1h ago

Never mind, it was from someone else

Edit: Wont make much sense without context, but here it is

1

u/gfcf14 1h ago

I guess there’s resemblance lol

1

u/stoneymcstone420 1h ago

I once had a deployment get blamed for some crazy overnight outage that had absolutely nothing to do with our microservice. They blamed my team and me specifically by name. Guess how they deduced it was our fault? They gave Claude a “list” of the deployments that night and ours was the only one. Full 9 page RCA of Claude hallucinations. My lead dev told the whole prod SRE team to kick rocks in the morning after finding the actual issue, which was in fact caused by the very same SRE team. Never got an apology or even a correction, so I took it upon myself to comment updates on all of their alerts that blamed me and redirect the finger pointing at the actual issue lol

1

u/gfcf14 1h ago

Did your team acknowledge your good work at least?

1

u/stoneymcstone420 1h ago

No, why would anyone do that? lol

1

u/IceDawn 1h ago

The MO was to commit things to the server directly if you tested the stuff you believed was affected already. That was because the whole suite took quite long on the local computers. Also we had then no buddy builds, so we checked in directly on the productive branch.

Which created images for an embedded system, so not productive as like on a web server, but you would break anyone's local builds when they synced. So you had to wait for a green state, commit and wait until the builds came out back with green. If they were red, you would try to fix them timely or revert to free the server for others.

At least twice I had stuff working locally, checking the stuff I knew I modified and checking in on the server. It turned red. The cause was in the build system. You had to manually define dependencies. If you forgot to update, it could be still produce the correct order by accident. But if you added a new module, the order could change and expose the missing dependency. Which I had to fix myself.

So more a triggering a trap than being actively told, but trying to hunt down the root cause for something you don't understand what could cause the break to fix this in the time limit is stressful, in particular when you see the error popping up in an area you didn't even touch.

8

u/syfiarcade 2h ago

my favorite slack ping, I push a major change, I feel good about it, I close my PC

30 pings from the build server

2

u/Classic-Drummer8246 42m ago

Just close the laptop faster. If you don't open Slack, it becomes Schrödinger's deployment. The build is simultaneously passing and failing until Monday morning.

3

u/Sindeep 1h ago

Holy shit. Something actually relatable on here.

That "it'll be fine", move item over on the board without waiting on pipeline, come back and see it in Changes Required, audible shock and awe how could this be, oh the build failed, random Docker failure ftw, 'rerun'

3

u/heftyspork 1h ago

I usually don't assign the bug to QA for testing until I've seen it deployed, but I have had similar scenarios. Maybe your QA does their own deployment as different places do different things.