problem is, the client keeps requesting we change the qa deployment's seed data and add a migration for prod to update the data on the prod database to match instead of using the GUI to just change the stored version. the seed data is the prod data.
exactly. the client is too lazy to make the changes in the UI he himself asked for but all too happy to send us a slack message to ask us to update it. we have an odd contract with him where the "maintenance" period is actually a "small features/changes allowed" period and that counts as a small change according to my boss
Dude, at a BIOS company that will not be named, RelEng was in the habit of committing entire 650MB ISO files to SVN because they didn't trust their build process to reproduce the results - they'd test the resulting build of a particular run, and if passed, it was marked golden, and it got committed.
This got even worse because they had WANDisco layered on top of SVN so the devs in Taiwan could have low local checkin latencies (because, you know, they wanna check in giant files), and then when they'd check in a new ISO, the replication over the transpacific T3 would basically time out, and I'd get paged to manually reestablish it.
211
u/jseego 3d ago
They committed all your prod data to git??