Live data from Hacker News

Poll: How often do you deploy to production?

news.ycombinator.com

1–10 of 64 posts

Re: Poll: How often do you deploy to production?

#2
That's an odd question, really. It all depends on the context and the type of changes, obviously.

If it's a critical fix, then it goes out asap. If it's a minor fix, but relating to a new feature roll-out from 2 hours ago, it too goes out as soon as it's ready. Otherwise, changes gets deployed once the feature is complete.

Re: Poll: How often do you deploy to production?

#3
Enterprise stuff in the domain of insurances:

new version around once a month to production, datafixes whenever they are urgent. BI/DW & reporting side with quite a bit faster cycle, around once a week, as the requirements of the extremely complex metrics and dimensional data hierarchies are still evolving.

Re: Poll: How often do you deploy to production?

#4

That's an odd question, really. It all depends on the context and the type of changes, obviously. If it's a critical fix, then it goes out asap. If it's a minor fix, but relating to a new feature roll-out from 2 hours ago, it too goes out as soon as it's ready. Otherwise, changes gets deployed once the feature is complete.

I understand what you're saying, but I think the OP meant how often do you deploy on average. That is, take all the deployments you mentioned, regardless of the reason they happened, and average out.

Re: Poll: How often do you deploy to production?

#5
With my employer we deploy several times a day. We have 2 SVN repos. One dev, one live. To make a change live you commit your change to the live repo and it is auto-synced. I am not sure how we came to have this. When I first joined there was a code reviewer who manually pushed changes live. He quit and the server admin made it auto.

I wouldn't recommend this set up. I am incredibly competent. I make maybe 1 minor mistake a month - if that - so with me this set up is workable. The other developers I work with.. not so much. The main issue with this set up is newbie developers deploying what they thing is a good fix which breaks in lots of edge cases. Bad patches like that can take weeks to become apparent then longer to chase out of the system as there is no way to simply rollback.

For my side project I deploy every Wednesday. Every now and again there is a bug fix which needs to be slipped in on an odd day. I currently deploy manually because I haven't set anything else up.

Throw up maintenance page -> update database -> upload new files -> quick test -> remove maintenance page.

It is a bit time intensive but I haven't had any problems with it yet. I like to group changes so I can announce them on the same day.

Re: Poll: How often do you deploy to production?

#7
That is a tricky question.

here, we deploy a major update to the system every 6 weeks. All database changes go into the major update.

We release patches to production frequently. In first week of the major update we might do 5 - 6 patches per day.

This is not easy for us, as we do not have everything on the web.

We have a java application that is patched and downloaded from our users so we want to avoid forcing them to download the new stuff too often.

if it was a web application the impact of the patch would be minimal.

Re: Poll: How often do you deploy to production?

#8
Architect for a major US bank reporting in here:

Major changes: every 5 weeks (build for 4 weeks; test for 1) Minor changes: every week (urgent and emergency changes) Bug fixes: as needed. usually 0x/week but can be multiple times a day if necessary.

Mobile app releases: rarely. The belief is that frequently updated apps are considered a bad thing.

Post reply on HN