Re:“It's The Future”
by moron4hire on Wednesday August 17, 2016 @08:16AM
(#12304069)
That sounds more like your team doesn't know how to use git beyond nothing more than an SVN replacement.
[ Parent
| on HN ]
Re:“It's The Future”
by vertex-four on Wednesday August 17, 2016 @08:28AM
(#12304130)
"We rolled out this update with 220 changes. There's a breaking bug. Where is it? We need to find out in the next 5 minutes, revert, and deploy. Otherwise we have to revert the whole thing- we're losing money."
Git doesn't really help with that. More granular deployments do, and if microservices help with more granular deployments, go for it.
Re:“It's The Future”
by raverbashing on Wednesday August 17, 2016 @10:14AM
(#12304818)
> We rolled out this update with 220 changes.
That's your problem right here
Git-bisect does, doesn't it?
Only if you have a test that catches the bug and it still needs time to run. You'll also need time to write a fix, validate it and deploy. Plus any extra time your organization needs between code and deployment
It helps with the find part. The revert and deploy not so much, especially say if it's the middle commit if 200 and you'd still like to deploy all the commits before and after.
Re:“It's The Future”
by vertex-four on Wednesday August 17, 2016 @09:16AM
(#12304400)
If you had a test for the issue, you probably wouldn't have deployed the software in the first place.
My experience is that most devs don't even know how to use SVN correctly. I just had a conversation with someone waiting for me to finish something before they could branch. The idea that I could merge my change into their branch afterwards didn't occur to them.