We're in e-learning and we normally deploy to production once a month, usually with one or two following bug fix deployments. Most of the process is automated with our CI, but we still have some manual action steps required.
Poll: How often do you deploy to production?
11–20 of 64 posts
Re: Poll: How often do you deploy to production?
#12Architect 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.
Interesting report. It's a bit off-topic but I think at least with the AppStore Apple failed to separate bug-fixes (minor) updates from major ones - creating the feeling that updates should be kept to a minimum.
Regarding your backend, are you using any type of CI?
Re: Poll: How often do you deploy to production?
#13We have a productized SaaS, where the product UIs are sometimes updated several times a day each (we have a couple dozen products now and growing). The backend driving the products is updated usually on a weekend after a 2-week sprint. It works out pretty well for us, and we rarely feel rushed to get something out. There is the odd hotfix for a critical bug - that happens maybe once every two months or so.
Re: Poll: How often do you deploy to production?
#14I hand it over to the lead dev who is the only one of the contractors with sufficient security clearance to access the production systems. His process is less automated than I like and patching production bugs can be a pain.
I only hand over work to him on the proviso that my work is ready "pending end user acceptance testing". Of course there's still the traditional 2nd of january deploy untested code manouver they seem to love. Last time they pulled that it cost them at least $40k but they were warned and we weren't fired.
Re: Poll: How often do you deploy to production?
#15Investment baking web software; at the moment, every two weeks - code freeze + packaging is done on tuesdays, packaged release is about a week later (after being deployed to acceptance and getting stamps of approval from management that click through the app once or twice or something). I think we can do much faster though, weekly at least, and continuous if we improve our processes and discipline.
Re: Poll: How often do you deploy to production?
#16Depends on whether or not I'm actively working on a new part of the site. It varies from 10+ times to 1-2 times an hour.
However, with all these people talking about deployment, I just wanna hijack (sorry!) and ask if anybody can help with my current deployment setup:
- Branch into a new feature (refactor-javascript for example) - Commit constantly - Rebase with master then merge into master - Push to remote repo - SSH to server, and then pull from the same repo - (.git isn't exposed via HTTP)
What's the better way of doing this? If you could help that'd be great :-) Drop me an email at andy@fine.io
Re: Poll: How often do you deploy to production?
#17That'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.
[deleted]
Re: Poll: How often do you deploy to production?
#18Depends on whether or not I'm actively working on a new part of the site. It varies from 10+ times to 1-2 times an hour. However, with all these people talking about deployment, I just wanna hijack (sorry!) and ask if anybody can help with my current deployment setup: - Branch into a new feature (refactor-javascript for example) - Commit constantly - Rebase with master then merge into master - Push to remote repo - S…
We never rebase like that, and instead use git merge master --no-ff
We also never SSH into a server, and instead use Capistrano to handle this for us. Capistrano works great with Rails, but even other frameworks have plugins to handle this. And if you're new to capistrano, take a look at http://capo.io (shameless plug: we built this) for readily available recipes for all kinds of tasks. We use Capo for all our projects, ranging from static sites to jekyll to sinatra, rack and rails apps.
Re: Poll: How often do you deploy to production?
#19One week minimum to get through change control and schedule a release, plus a week of development and testing means only 2 non-emergency releases per month. But given the effort involved, usually once every 4 to 6 weeks.
Re: Poll: How often do you deploy to production?
#20Support Lead (and the "Application Expert") for an Oil-Major internal web app here:
"support fixes" - ASA(F)P, after 2 rounds of testing and several sign-offs + Management approvals.
"Change Requests" - Deployed after an impact+risk-assessed notice period (between 1 - 14 days), and after the above testing/sign-offs/approvals
"New Release" - Should be Quarterly, after several rounds of testing, sign-offs, agreements from all affected business units... but there's been a big push on the app recently, so there's been 3 releases this year so far.
And then we have to go through all the testing/sign-off/deployment stages again with any Joint-Venture companies that have their own installations due to local data laws.