wake up this morning.
logon to work computer to find code that shouldn't have gone to production yet.
is in production...
it failed. because a new table didn't exist in the database yet.... that this job needs to read....
WTAFF.
Is it a monday? It feels like a monday...
@crazyuncleharris Morning 🙂 There are idiots all around us - hope you can fix production quickly.
@Mandypar we got it figured out,
Wouldn't call the guy an idiot by any means
However some of our processes are pretty idiotic and changing some things is like pulling teeth, but it is happening at all levels thankfully
Our QA department finally passed a simple fix that has "existed" for almost a full year
"Do not print out credentials 2 console"
they finally readied it for prod
However my change (which uses the above .dll file) was also in testing. So they just pulled that 2 production 1/2
@Mandypar which would have been fine had my change not needed to depend on another change that isn't ready for prod yet.
So like fun.
We need to standardize and automate in our change management software, the names of jobs & what their dependencies are.
But heyo that's a battle for another day, and not one I want to pickup the sword for as it would be huge & I have enough things on my plate that I'm trying to modernize & just down right improve(& watch blow up in my face time to time) 2/2