Hey Shrayansh ,You had told that you won't make other than Interview questions as private .But you made one of the most important topic : Concurrency Handling as Members only .This is not fair yaar
6:52 I think we need to merge hotfix version(v1.1) from master to develop branch(v2) as well when we are back merging to release branch(v2) or back merge release (v2+hot fix) to develop (v2).otherwise if a new release(v3) is created from develop(v3)..it might have lost hot fix update(v1.1).
Hi Shrayansh..thnx for the video. Query: Is the only use case of master branch is when we get a bug in prod and regression testing is going on in release branch?
I don't see anything useful when it comes to a scenario where we have multiple features under development in parallel and we go for release any of them to production
Hi, My question is that suppose have V1 feature on all the branches. Then we develop a new feature on V2 on dev and push to release V2. After that develop a new feature V3, V4, V5 and Pushed to Release. Now the Dev and Release branch are synched. But now, we want to deploy only feature V3 from Release to Production. How to do that without creating hotfix. Thanks in advance
Nope, the usecase where we merge hotfix (or in this case say bugfix) in release when new build is in Live and during monitoring we find an issue, and we want to fix on top of that new release only. Till backmerge is not done, new release and regression can not start.
@@ConceptandCodingSo generally after we have built some features in team, then we follow some testing of our features. With respect to that I have seen teams doing BUG BASHING. I wanted to check if you know how it should be conducted?
thanks - when we create the hit fix branch out of master branch for production issue- where/ which environment are we testing the "hot fix" before pushing to production again? given Dev & lower environments has exsiting new features being tested?
Hi alen, thanks for the super thanks. Means lot to me. Once we have created the hotfix branch out of master, we can test it on stage environment (QA) In stage environment, you can deploy the component which you want to test and run your FT or particular scenario from postman and get validate it.
@@ConceptandCoding thanks for replying- so based on your input - in that case - does QA contain both new features (version 2,3 being tested) + hotfix code? or ONLY the hoxfix code? (version1 +hotfix code) - will this interupt the regression? and what if there is conflict between hotfix and new features?
@@alen740926 regression is happening with Release branch manifest(which has feature 1 and 2) and Hotfix is happening with Live changes + Bugfix changes. Release regression can go in parallel with Hotfix manifest regression
@@ConceptandCoding so basically - use hoffix branch to manually deploy into QA environment (obviously we need to cooridnaten with developers to not push any other changes to QA during that time) while regression can still be going-on in UAT/release branch...? and once verficition is done in QA then we can use hotfix branch for production issues...
let me work this weekend buddy. Or pls ping me on linkedin, we can discuss for 15, 20 mins, if you have any doubts with concurrency, hope i would be able to answer those. Good luck for your interview.
Thanks a lot for the video . In our org we don't keep release and master separate . Mine is not MNC though. But i feel there are certain advantages for the same. First in case multiple teams are deploying in prod in same day then it becomes difficult to monitor to separate release version on prod. Second in our org we have restrictions on which branch can be deployed in prod . We can only deploy master in prod. This helps to maintain consistency . Also it becomes easier to find out what is the diff btw code in prod and qa envs. Lastly on the point of hot fix. we do have a lot of hotfixes but usually we don't face problems with same because any hotfix will be merged via pr and the code diff will always show the changes. Not sure if this is a correct way but is working for know. Please let me know your pov on this or why it may not be a approach . Also Shreyansh if possible can we have a community channel of discord /slack . Have a lot to discuss with you 😅. Thanks again for all your informative video.
