Master(main branch for), feature branch for added functionality. Release branch for delivery to customer, instead of building application from master we build and deliver to customer from release branch. Master branch is for active development. Master branch can be for testing.
Abhishek Sir, we are on our way please keep making videos don't lose motivation in future this playlist will be one of the best tutorial on RUclips trust me.
It's truly fantastic to have the opportunity to learn the DevOps course with real-world examples, which are often not offered by other institutions. Thanks Abhishek 😊
Thank you so much sir you are doing really great thing. Outside other institute charge for devops to learn many of the students who want to learn devops they are not able to learn devops because they can't afford fees that much but you are teaching free so that they can learn really it's great thing sir. Thank you so much once again.
It's truly fantastic to have the opportunity to learn the DevOps course with real-world examples, which are often not offered by other institutions. Thanks Abhishek 😊
Thank you so much abhishek ...actually now I came to know about your channel but it was really good and very simple way to understand your all concepts definetely i m going to watch all devops videos ,u are done great job thank you so much again lots of gratitude🌸
Super brother your explanation and your example, already i referred your channel to my friends keep it up thank you for providing this much of knowledge to us with free of cost 👏👏🙏🙏🙏🙏🙏🙏
Abhishek sir, you can also put contribution for your effort. We can contribute some amount for you. It's for our satisfaction. If anyone wants to contribute, they will do. Because every institute will charge a lot of money. But you are teaching without fee.
Thanks for the feedback.. Right now the intention is to not charge from the students :) But because many students are asking .. I will check what is possible :)
@@SharanlingMajge It's just contribution to the channel bro. Not like you have to pay to view the course. It will be free only and if anyone are really interested and to support his cause, they can pay. That's it.
hi sir, thanks for your time to guide us! This what i understand. The default branch we call it as master branch. under the master branch will be another 2 sub-branches 1.development branch and 2. release branch. 1. development branch --> we create an feature branches as per the devlopers team size. 2. release branch --> through this branch will release to production. if bugs in prod. will create the hot-fix branch under the release branch. Thanks.
hot-fix branch is created for quick bug fixes or adding quick features ,and then it merge in release and master branch to kept it up to date .....am i right sir....plzz reply to me sir
Thanks for explaining the branching strategy. Could you please explain how this branching strategy to be used for deploying applications in various environment such as Dev, Test, production environment etc..
Really love like video. It is easy to understand, and I now have some clarifications on some things I was confused about. God bless you for this effort
Just a quick question - Release branch would most likely would have just commit that is common to the master branch commit where one decides to branch for release. No further commits would go in Release branch from that point forward and new commits would go to dev branch (main/feature) and later on new release branch would be created when ready for release? Is my understanding correct? Thank you for these videos Abhishek.
Abhi shek now iam thinking why i didnt find you one year back. Now i got to know your lectures one year back i took a course from intellipaat , those guys also not taught like this
Hi Abhi It was a greatest stuff I could say. And I would like to thanks a lot. Are you sure this course will definitely will add a clear demo of What's involved in DevOps. I would like to thank you a lot for you initiative to support many for free.
Hey, Abhishek, very helpful videos and nice clear explanation on GIT branching strategy. I used to work as Front-end developer mainly when pushing codes, I used to face problem like let's say Dev 1 is working on feature "xyz" and Dev 2 is working on another feature but dev2 is dependent on Dev 1 feature does Dev 2 needs to wait until Dev1 finishes developing feature? Or dev 2 can go head and create separate branch / same branch as Dev1? and start working on developing feature Dev2 pull code after Dev1 finishes and everything has been pushed faces lot of Merge conflicts? how to avoid Merge conflicts? any Git commands to check before avoiding merge conflicts?
Thanks 🙏 so much. But I have one doubt to clear, how would you compare main, dev, staging and uat branches to main and releases branches covered in this video? Keeping in mind that feature and hotfix branches are common to both? Thanks once again. You are a healing to many
Hi Ahbishek, It was really amazing if you had chance to do video on complete real time pipeline using groovy to deploy in qa uat prod with the help of jenkins shared library so that i t would be very useful to crack any devops interview
Hi Abhishek, thanks for the sessions.. in the previous videos u told abt the github test repo. while practising, i found some other options in GIT.. desktop app o GIT.. how is it diff. can we use the desktop app as well.. please make me understand. TIA😊
Hi Thanks for the detailed video , If we get an issue in production shortly after a release, you mentioned we can create a hot fix branch and release that branch on to prod. Any downside if use same release branch which was used for actul release instead of creating a new branch ? assuming we use hot fix branch , what's the order of commits to give the fix, would developers make commits first in hot fix baranch or master or release ? what's the source branch for Hot fix branch ?
Thanks once again Abhishek, could you suggest which is the bes strategy ? i heard names like Git flow strategy /Git hub flow strategy/ features branching strategy? We discussed about Git flow strategy in our video am I right?
Hello, Thanks for the great video. I would like to know new versions are only deployed from Release Branches? Main branch is not used for deployment? Is main branch only for maintaining all codes of versions?
It’s very clear and perfect explanation thanks abhishek I have one small concern so the organization when ever a product is ready for a customer phase they create a release branch and they go ahead for release and then they keep updating the master branch whenever they are ready with other version again they create release branch and then host it so that they can continue testing and do improvements on master branch.. so according to this video there might be more than one release branches right ? This is what I understood if I am wrong please correct me !!! I will be waiting for your response Thanks in advance!!!!
Hi Abhishek, video is really very informative, just a doubt before creating release branch if I want to omit any feature branch which is already merged to master, but I don't want to deliver that to customer part of current release, then whats the best way to do that.
Hi Abhishek Sir, @18:19 in the Uber example, will the 'feature-bike' branch be merged into the latest master branch or into the master branch from which it was originally created?
Hi @Abhishek, have been following your DevOps tutorial and reffered to friends as well to get knowledge from best place. Currently following the same branching strategy for my client, however application requirement here is to rollback to last two successful release version (N-2) instead of previous version. In this case could you advise, how to manage release branches or tags to use please.
Hi Sir, Just one query How this branches works in different different environment, ? like Dev,QA,Pre-prod,Prod ?? which branch goes where ? & how deployment will happen..please help on it..
Master(main branch for), feature branch for added functionality. Release branch for delivery to customer, instead of building application from master we build and deliver to customer from release branch.
Master branch is for active development. Master branch can be for testing.
that's the way we've done it....
This channel is Gem for Devops mastering, I appreciate your efforts, Good work!!!
Abhishek Sir, we are on our way please keep making videos don't lose motivation in future this playlist will be one of the best tutorial on RUclips trust me.
Awesome. Please share the videos with your friends
It's truly fantastic to have the opportunity to learn the DevOps course with real-world examples, which are often not offered by other institutions. Thanks Abhishek 😊
Thank you so much sir you are doing really great thing. Outside other institute charge for devops to learn many of the students who want to learn devops they are not able to learn devops because they can't afford fees that much but you are teaching free so that they can learn really it's great thing sir. Thank you so much once again.
It's my pleasure
My vocabulary is not enough to Praise You....Thank you so much sir
😍😍😍
It's truly fantastic to have the opportunity to learn the DevOps course with real-world examples, which are often not offered by other institutions. Thanks Abhishek 😊
Great to hear!
Thank you sir....the way that you are explaining is understandable to anyone with no knowledge.
Thank you so much abhishek ...actually now I came to know about your channel but it was really good and very simple way to understand your all concepts definetely i m going to watch all devops videos ,u are done great job thank you so much again lots of gratitude🌸
Super brother your explanation and your example, already i referred your channel to my friends keep it up thank you for providing this much of knowledge to us with free of cost 👏👏🙏🙏🙏🙏🙏🙏
Thank you so much 🙂
Great Uber example, Explained well.
Thanks !!
Completed Day:10 Video and Practice also done.
Thanks Veeramalla garu
GK from NJ
Thanks a lot !!
Abhishek sir, you can also put contribution for your effort. We can contribute some amount for you. It's for our satisfaction. If anyone wants to contribute, they will do. Because every institute will charge a lot of money. But you are teaching without fee.
Thanks for the feedback.. Right now the intention is to not charge from the students :)
But because many students are asking .. I will check what is possible :)
Pls don't do that..just know I started...I belive many more people too...collect from those who have overflowing money
@@SharanlingMajge It's just contribution to the channel bro. Not like you have to pay to view the course. It will be free only and if anyone are really interested and to support his cause, they can pay. That's it.
hi sir, thanks for your time to guide us!
This what i understand.
The default branch we call it as master branch.
under the master branch will be another 2 sub-branches 1.development branch and 2. release branch.
1. development branch --> we create an feature branches as per the devlopers team size.
2. release branch --> through this branch will release to production.
if bugs in prod. will create the hot-fix branch under the release branch.
Thanks.
Awesome. Great learning Akhil
Hi Abhishek, Thanks for the explanation , However how would be this scenario looks if we have like Dev, QA,Stageing and Prod servers?
hot-fix branch is created for quick bug fixes or adding quick features ,and then it merge in release and master branch to kept it up to date .....am i right sir....plzz reply to me sir
Hi Abhishek veeramalla I had just started exploring your playlist, you are simply an amazing mentor
Thanks a ton
When i heard the word "Git Branching Strategy" i thought it is very hard to understand. But you made it simple and interesting thanks Anna🙏
Glad it was helpful!
Thanks a lot. your doing great job . I appreciate your efforts , I tell you bottom of my heart.👍👍
It's my pleasure
Hi Abhishek excellent session. Thanks for brushing up my git knowledge.
My pleasure
I understood branching strategy clearly thanq so much abhishek for you your efforts to make understand the concept of branching
Beautiful Explanation 👍👍👍👍👍
Thanks and welcome
Thank you so much for this video, got my concepts cleared related to branching strategy
Great to hear!
Thank you so much abhi sir, got the complete understanding of the concept.
Completed this Video on 29th June 2023.
❤️❤️
Really good explanations. Thank you.
Thankyou for the stuff but if you have showed practically that will help a lot more to the people....TQS bro
Thanks so much sir you’re doing a wonderful job
It's my pleasure
Thank you Sir, I got the same question and explained exactly, though am working i didnt had this much idea,it is realy helpfull..
Learned something new about Git which I was unaware of until today.
Awesome
Content was really good 👍
Thanks
Wonderful explanation!! Truly thankful 👏
Glad it was helpful!
Completed day -10 successfully
Super anna....Neet ga explain chesaru.
😍
Thanks for explaining the branching strategy. Could you please explain how this branching strategy to be used for deploying applications in various environment such as Dev, Test, production environment etc..
Thank you so much. The explanation is fantastic and helpful. You are gonna be my mentor..
Happy to hear that!
Very nice explanation Abhishek bro....Keep on rocking the knowledge sharing...my lovly kudos to u
Thanks a ton
Thanks Abhi.. Clearly understood 😊
My pleasure 😊
so far the best video available on YT...thanks bro u r a savior...could u plz add or show how this branching strategy works in Jenkins as well?
Thanks alot
Learnt a great and new info thanks @Abhishek❤❤❤❤
Thank You Sir! Learnt something new !
Glad to hear that!
Thanks a lot. This is really good. I finally got it.
Glad it helped!
Thank you Abhishek 🙏
Awesome. Got this topic so easy.
Thank you Abhishek ❤
Thanks a lot for making this video Sir. It was superb with real world examples ❤
🙏🙏🙏❤ for ur dedication and teaching
It's my pleasure
Day-10 Completed successfully :) and Thank you Abhishek :) .
Thank you Abhishek, it's very clear
You're most welcome
Great explanation Sir.
welcome
Awesome content, keep it up Abhishek...Love and respect from Pakistan.
😍
Thank you bro, Very helpful.
Thanks a lot
You are God of devops sir
❤️
Superb, thank you
Welcome 😊
Really love like video. It is easy to understand, and I now have some clarifications on some things I was confused about. God bless you for this effort
Thanks a lot
Thanks a lot. very well explained with examples.
Just a quick question - Release branch would most likely would have just commit that is common to the master branch commit where one decides to branch for release. No further commits would go in Release branch from that point forward and new commits would go to dev branch (main/feature) and later on new release branch would be created when ready for release? Is my understanding correct? Thank you for these videos Abhishek.
Great Explanation,Very easy to understand.How can we add tagging to release branches ?
Very Helpful!😍 Thank you So much
Thanks Bhai!
Go On.
Thanks
Thank you for your presentation. How about the testing branch to validate new features before deliverying to customers?
Grateful😇 Thankyou Abhishek
Hope that today it 'll be practical session of branching strategy.
Hope you enjoyed video
@@AbhishekVeeramalla yeah bro
This is pure gold
Most welcome !!
Date- 21/08/2024 , Completed the video . FOund this a bit tough. Hopefully doubts will be cleared in upcoming videos.
Thank you.
Yup don’t worry move on to the next ones
Thank you sir
Welcome
Hi , great explanation? Are you planning to do any playlist for developers as a beginner?
Thanks ,its Clear concept.
Completed 10 days course.
Good explanation abhishek keep it up 👏👏
Thank you so much 😀
Thank you ^^
Abhi shek now iam thinking why i didnt find you one year back. Now i got to know your lectures one year back i took a course from intellipaat , those guys also not taught like this
Eureka is superior than those
@@Cloudnp9458 then y u r watching here
Thanks Shiva ❤️
Awesome, got you. It's easy
awsome
Thanks
I am watching from Noida Delhi ncr
Thanks
great explanation .
Hi Abhi It was a greatest stuff I could say. And I would like to thanks a lot. Are you sure this course will definitely will add a clear demo of What's involved in DevOps. I would like to thank you a lot for you initiative to support many for free.
Thanks alot .. Yes Sharif .. complete the course and you will get clear understanding of devops
Hey, Abhishek, very helpful videos and nice clear explanation on GIT branching strategy. I used to work as Front-end developer mainly when pushing codes, I used to face problem like let's say Dev 1 is working on feature "xyz" and Dev 2 is working on another feature but dev2 is dependent on Dev 1 feature does Dev 2 needs to wait until Dev1 finishes developing feature? Or dev 2 can go head and create separate branch / same branch as Dev1? and start working on developing feature Dev2 pull code after Dev1 finishes and everything has been pushed faces lot of Merge conflicts? how to avoid Merge conflicts? any Git commands to check before avoiding merge conflicts?
Thanks
Thanks alot Upendra
great seesion, thank you. I have one query - In github should we need to create hotfix branch from release branch or master branch?
Release
Thanks 🙏 so much. But I have one doubt to clear, how would you compare main, dev, staging and uat branches to main and releases branches covered in this video? Keeping in mind that feature and hotfix branches are common to both?
Thanks once again. You are a healing to many
Most welcome !!
Hi Ahbishek,
It was really amazing if you had chance to do video on complete real time pipeline using groovy to deploy in qa uat prod with the help of jenkins shared library so that i t would be very useful to crack any devops interview
Sure
Good content brother, it will be very helpful if you privide notes{your content and interview question and answers} also .
Ok next time
Well explained 😊 thanks
My pleasure 😊
Awesome. Please share the videos with your friends
thaank you
💐
Hi Abhishek, thanks for the sessions.. in the previous videos u told abt the github test repo. while practising, i found some other options in GIT.. desktop app o GIT.. how is it diff. can we use the desktop app as well.. please make me understand. TIA😊
Yes u can use that as well
Hi Thanks for the detailed video , If we get an issue in production shortly after a release, you mentioned we can create a hot fix branch and release that branch on to prod. Any downside if use same release branch which was used for actul release instead of creating a new branch ? assuming we use hot fix branch , what's the order of commits to give the fix, would developers make commits first in hot fix baranch or master or release ? what's the source branch for Hot fix branch ?
you r god of devops
❤️
Thanks once again Abhishek, could you suggest which is the bes strategy ? i heard names like Git flow strategy /Git hub flow strategy/ features branching strategy?
We discussed about Git flow strategy in our video am I right?
Yes, you are correct
@abhishek : Is this called Git flow strategy which you have explained
Pls clear my doubt…
Btw it was great explanation thank youu
Hello, Thanks for the great video. I would like to know new versions are only deployed from Release Branches? Main branch is not used for deployment? Is main branch only for maintaining all codes of versions?
Release branches, yes.
Main branch is for active development
@@AbhishekVeeramalla Got it. Thank you!
Day-10 done ✅️🙂
Keep Going..
It’s very clear and perfect explanation thanks abhishek
I have one small concern so the organization when ever a product is ready for a customer phase they create a release branch and they go ahead for release and then they keep updating the master branch whenever they are ready with other version again they create release branch and then host it so that they can continue testing and do improvements on master branch..
so according to this video there might be more than one release branches right ?
This is what I understood if I am wrong please correct me !!!
I will be waiting for your response
Thanks in advance!!!!
Yes there will be multiple release branches
Great video :)
Hi Abhishek, video is really very informative, just a doubt before creating release branch if I want to omit any feature branch which is already merged to master, but I don't want to deliver that to customer part of current release, then whats the best way to do that.
i completed this video abhishek
Abhishek,could you just show a practicals on merge and rebase.
For sure
sir can you please explain the difference between trunk based and gitflow branching stratergies
hi bro if possible can you please do Realtime hands-on videos so its help full to us
Ya sure .. will do more
nice
Thanks
Hi Abhishek Sir,
@18:19 in the Uber example, will the 'feature-bike' branch be merged into the latest master branch or into the master branch from which it was originally created?
Hi @Abhishek, have been following your DevOps tutorial and reffered to friends as well to get knowledge from best place. Currently following the same branching strategy for my client, however application requirement here is to rollback to last two successful release version (N-2) instead of previous version. In this case could you advise, how to manage release branches or tags to use please.
I can help you, but I will charge you 1000 rupees hourly.
you meant multi branching for microservices application according to your explanations. Right?
Hi Sir,
Just one query How this branches works in different different environment, ? like Dev,QA,Pre-prod,Prod ?? which branch goes where ? & how deployment will happen..please help on it..
The branches should be common for all environments. There should not be any environment specific branches and it is an anti pattern