News for hackers. Stuff that matters.

A comment on “It's The Future”. Parent comment

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.

[ Parent | on HN ]
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

[ Parent | on HN ]
Re:“It's The Future” by gmfawcett on Wednesday August 17, 2016 @08:50AM (#12304219)
Git-bisect does, doesn't it?
[ Parent | on HN ]
Re:“It's The Future” by Xylakant on Wednesday August 17, 2016 @08:56AM (#12304257)
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
[ Parent | on HN ]
Re:“It's The Future” by imron on Wednesday August 17, 2016 @09:02AM (#12304307)
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.
[ Parent | on HN ]
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.
[ Parent | on HN ]