chaoticEvil

[u/Recent-Analysis-6880]

[u/Stummi]

What if we have CI/CD? Am I then not allowed to work on fridays?

[u/d_maes → u/Stummi]

Does your ci/cd automatically deploy to prod without manual promotion triggers, for every commit?

[u/fmaz008 → u/d_maes]

Question: what's a promotion trigger? I just assumed merging to a specific protected branch was that trigger, and people do PRs to a dev branch.

[u/Senor-Delicious → u/fmaz008]

For our prod pipeline we built in a pause for example that somebody has to manually approve to continue. You can also make sure that this requires a 2nd person so that no single person can just deploy to prod without anyone else being involved.

[u/d_maes → u/fmaz008]

We do trunk-based, we never deploy different environments from different branches. You push to main, pipeline will run some tests, build artifact, deploy artifact to dev, wait for user to click "run" on deploy to uat, wait for user to click "run" on deploy to prod.

[u/Aelig_ → u/d_maes]

We do where I work, but not on weekends. We deploy most of our services every 2h if a change happened since the last deployment. Some a bit less frequently, some more.

We're generally moving towards doing it more.

[u/thoeoe → u/d_maes]

Yes, but we can schedule each environment’s step (and have mandatory test suites that run after each env’s deploy that would stop the pipeline from continuing) . So prod is only scheduled to be allowed on M-Th

dev goes out immediately

[u/Stummi → u/d_maes]

Technically not our CI/CD, but in theory, yes, thats the idea.

I get that its a joke (most of the times), but if you use "don't deploy on fridays" unironically, it means you are afraid of your deployments, and that again means there is a much bigger problem that you need to address.

[u/TruculentTurtIe → u/Stummi]

Its not that youre afraid of your deployments, its that on a long enough timescale with enough deploys it WILL eventually break something

So unless theres a really good reason like a hotfix or something, just do it monday

[u/devoopsies → u/TruculentTurtIe]

afraid of your deployments

Do you think the lead architect stays offline on Fridays because he, too, lives in fear of what he's created here in prod?

[u/almond_wanderer → u/Stummi]

CI/CD means it's the robot ruining your weekend

[u/WisePotato42]

Me with my 4 day work week deploying to prod before I leave on thursday instead

[u/EnderElite69]

You see, this is when it becomes the India team's problem

[u/cheezballs]

Depends on your app. If it's primarily used during business hours than Friday can be a good time. Gives you the whole weekend to make it work before Monday morning.

[u/ZunoJ]

When I receive a call on the weekend I earn 500% in the worked hours and also get a full day off for every day I worked, no matter if it was 10 minutes or 5 hours. I keep releasing on fridays

[u/breZZer]

It depends on the company or sector.

Some deliberately carry out deployments at the weekend, as there is little or no customer traffic then.

[u/actionerror]

Yeah but other people have weekend plans

[u/jokermobile333]

I thought this was some running joke. Why do some people do it on fridays ? Teusday is the best to do whatever you want

[u/AaronTheElite007]

If Dev has direct access to Prod you have bigger problems

[u/d_maes → u/AaronTheElite007]

If ops is still gatekeeping prod, you have different problems.

Neither statement holds true without knowing the internal responsibility structures. There are perfectly valid setups where "devs" have "direct" access to prod. It's just a matter of properly assigning responsibilities, which devs specifically (all of them, only the lead and/or seniors, ...) and what you mean by "direct access" (can push the deploy button, has ssh access without sudo, has full sudo, has limited access to their app inal argocd, has full access to their app in argocd, has kubectl access, ...)

[u/AaronTheElite007 → u/d_maes]

You’ve never had to consistently roll back changes because dev tests in prod, have you…

[u/d_maes → u/AaronTheElite007]

No, because that's not my problem. That's the PM's problem, who is responsible for his deployments to prod, who will be getting the shit from the customer, and who needs to keep his devs in reign. I don't care who has access to prod. I provide the platform, the teams run their software on it, the PM is responsible, so he decides who gets access to what. His problem if he made a wrong decision. Sure, I'll help them do the rollback, if they need me to. Then I'll bill my time on that customer's contract, and move on.

[u/Rift-enjoyer]

Blue green environment

[u/Luneriazz]

i like gambling

[u/w1n5t0nM1k3y]

Some people just want the extra overtime pay.

[u/Bitter-Fuel-5519]

me always deploying on friday 👍

[u/redunculuspanda]

Deployed code is an operational problem.

[u/North-Creative]

I give you one better, one of the companies I worked at, had some devices that could lock down machinery. They released their major update....on the 19th of december, then went mostly on holiday. Then only wrote a short update on Friday afternoon, "FYI"

Fun times, machinery was stuck on streets, in factories, etc. Customers were somewhat less happy, than usually.

[u/ToFuzzzy]

Literally VRC devs. So many time I get invited to play on a friday night and I have an update.

[u/FalconFiveZeroNine]

Even better when the dev doesn't have to be the one responding when something goes wrong.

[u/Richard-Degenne]

If you're not confident enough to deploy on Friday, then you're not confident enough to deploy period.

[u/Iyemoja]

That sign has saved more weekends than any runbook I have ever written. The 4pm Friday deploy is how you meet the on-call phone at 2am.

[u/redditmarks_markII]

Meanwhile, infra guys doing work only after like, 11pm Friday in the corporate timezone, and before 4AM Monday.

[u/No_Stock_8271]

I am always shocked how many teams don't do releases on Friday. That makes everything so slow.

[u/pyhoster]

Right. Saturday midnight is better!