The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
A few weeks ago, manager asks me to set up a job to run daily in QLTY. After various forms and conversation, job is set up.
QA says this project is "out of scope" for them, so they don't need to test it.
I submit a "cancel daily job run"
Manager is now out of town and is the only person that can approve the cancellation.
Job fails (missing DB tables) but I don't get notified because I'm not part of the job fail notification group.
There are three other jobs waiting after my failed job that won't kick off.
Another email from someone else about my failed, pending cancellation, job holding off other jobs.
Email goes out asking why production jobs are being held up by a QLTY job.
Email goes out that the person setting up my job created it as a predecessor to a PROD job.
I get blamed, since I apparently requested my QA job run before the PROD job. Actually, it was the IT person who suggested it, and I agreed, not realizing I was mixing apples and oranges.
Email goes out asking if there's someone else that can approve the cancellation because the manager is OOO.
Email goes out saying you have to email "ESD Leadership" to get an approval change.
That email includes a wrist slap (but oddly not at me) that jobs shouldn't be created if they're not ready to be run. Well, it was ready to run, but the I realized some DB tables hadn't been created (I can take the blame for that), so it failed.
Email goes out that the "ESD Leadership" is also OOO, so it'll have to wait until Monday.
Email goes out that the approval can be escalated to the VP or set the job to "normal" so the successor jobs can run.
Manager emails that there weren't any dependencies on the job when it was approved. But manager had berated me for not filling out the form correctly with predecessors / successors.
That's what was sitting in my inbox this morning. What were we talking about regarding "ideology"? Basically, all someone had to do was tell the job to off, problem solved. But nooooo....
He's writing up the process in a short 100 page document.
You must have this signed by only 3 of your 7 managers.
Please join me in celebrating this newly streamlined process with a brown-bag lunch which you are required to attend. Food will not be provided.
Definitely Usually, when I've seen this phenomenon its some security "expert" locking everything down so tight that no one can get any work done. After all, the most secure system is one you can never access
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.