This is my punishment for wanting to deploy on Friday afternoon 😎 #salesforce
I had a colleague years ago where we had an understanding for the system we designed, built, and supported - soup-to-nuts - that nothing was to be implemented, no matter how small or trivial on a Friday. I don't recall what the catalyst was at this point, but she and I held steadfast to that rule for the 3 years we worked together - no matter who was asking (demanding) or how 'easy' it would be (like a picklist value add). We'd been burned once - but not again. We just wouldn't do it. And neither of us lost a weekend to such an issue ever again. The end! Valdas Stasevicius Salesforce Siebel Systems
Looks like somebody skipped running test classes in a full copy!!
It'd be even worse to just be 1 error, but in a Profile file, so you have to fix each error one at a time, and deployment takes an hour each time. 😅
Godspeed brother 🫡
Switch to automated ci/cd with the mindset of deploy anytime. You want to deploy friday do it, if it fails you fix it monday. If it’s critical it has to be in for Monday, it should have been deployed the Wednesday before which gives you 2-3 days of wtf time. Oh and make sure you run all the unit tests in preprod/QA if not it just doesn’t work.
You have been warned. Friday afternoons are for gazing out the window, looking forward to the weekend - not doing deployments!
Better to Validate during weekdays to avoid last time rush Also avoid promoting low code coverage piece test classes in higher sandboxes, so that at the time of Production validation these issues can be minimized.
We switched to gearset and it made catching apex issues easier. Lol
When you got 99 potential problems and a successful deployment ain't likely to be one.
Business Operations Manager at Colossal, LLC
1moWe have been using ChatGPT 4o to write test classes. We drop the Apex Class in the Prompt and tell it to write a test class that has 75% code coverage. Worked every time so far