why does amazon work on mainline instead of creating branches?
Aug 17, 2020
15 Comments
how do people working on multiple features work on their items parallely?
why is amazon promoting such technical path?
why not branching and merging??
comments
The reason why you see people work directly on mainline is because they are either rushed on time or suck at git.
You can have a testing environment that is not local that consumes from the remote branch. The reason that the environment is not local is because it runs integration test with other services and you cannot crest locally for various reason.
Or you have a pipeline that runs load test, and pipelines consume remote branch.
The only branch which is allowed to be consumed by your real env stages is mainline. You might have a special feature that requires load testing etc and there it makes sense to have a separate remote branch. But that is a special case imo. Most features do not and should not require this. Btw you can call other services from your local env as well (as long as both are in the same fabric).
I might make some assumptions: is mainline == master?
I am joining Amz very soon so any guidance is appreciated
Review is done before you push to mainline. Not sure about ownership here. Care to elaborate please ?
The CD pipeline is set to a specific branch, usually mainline, and we merge to that branch in order to deploy.