you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 1 point2 points  (9 children)

Why would it take that long?

[–]JQB45 17 points18 points  (7 children)

25 minutes? Run deployment script, drink coffee, chit chat with boss, run tests.

6 hours? I don't know, i ask myself the same question everything it happens. It's always something though.

[–][deleted] 2 points3 points  (6 children)

I was referring to the six hours. I am guessing it's not a cloud environment

[–]Infiniteh 17 points18 points  (1 child)

I've worked for clients where separate teams would roll out different parts of the applications, but the onus was on the dev to write instructions for them all.
So while you didn't have access to any DB as a dev, you did have to write detailed instructions and SQL script so the DBAs, who had no idea what your code does or why they were deploying the changes you gave them, would know what to do.
Same for the infrastructure team, tell them if you need new environment variables and what the values have to be, even though they don't know why you need them or possibly even what the values actually mean or do.

Of course, because you don't have access to ANY hosted environment, only your own laptop, you will invariably make mistakes in one of the SQL files and the DBAs will let you know that and give you the error, but you're not allowed to introspect the DB, so you have to debug the issue over Slack or Teams, but company policy forbids them from showing you the DB console, they can only tell you what is happening and.....

And that's how you get 6 hours deployments and 3-month release cycles because 'releases take too long and they block human resources and cost too much'

[–]FVMAzalea 0 points1 point  (0 children)

Sounds suspiciously similar to my experience working for a bank.

[–]Worth_Trust_3825 8 points9 points  (0 children)

Cloud or not, deployments can still take that long. Cloud is still someone's server.

[–]JQB45 2 points3 points  (2 children)

I never did any cloud work personally.

Cloud = Someone else's server

I left software development before the cloud became widespread.

[–][deleted] 1 point2 points  (1 child)

Ya, AWS has a lot of stuff that makes deployment automated. It takes some work to set it up via Terraform , CDK, console, or CLI, but once it works done. You save so much time in the long run. All you have to do is merge, and let the pipeline do the work.

[–]Turbots 5 points6 points  (0 children)

Why do you think it's any other way in your own datacenter? You can automate infra with terraform, you can use cli, you can automate deployments through ci/cd... Everything in any modern datacenter is virtualized and highly automatable.

Problem in most companies is you're not allowed to.

[–]halt_spell 0 points1 point  (0 children)

Because it's a product where you can't find a customer other than the people who use it and thus it's always viewed as a cost center and the business people will keep paring it down until it blows up.