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.
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. - Simplified by CloudNP9458. Thanks for another great lecture @Abhishek Brother. ❤
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.
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 😊
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 👏👏🙏🙏🙏🙏🙏🙏
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 😊
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
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🌸
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..
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.
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
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
I think one more to add here we will have development branch where the developers will develop the code daily and when required they will merge the code to master branch. To sum up we will have Master Branch, Hot fix Branch, Development Branch, Feature Branch, Release Branch
While listening to this, I got question in my mind like enhancements are released via release branch and what about Master?I stopped and was scrolling for relevant comments.After that resumed and got the answer at 15:03 😆
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 🙏 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
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.
Your understanding is 99.999% correct ! 🤓 ✨ Branching for Release: When we create a release branch from the main branch (like "main" or "master"), it's a snapshot of the code planned for release 🚀. This branch should be as stable as possible. 🛠 Changes to Release Branch: After creating the release branch, it should only get critical fixes or final tweaks for the release. No new features or big changes go here! ❌✨ 🔄 New Development in Dev or Feature Branches: All new features or improvements continue in "dev" or feature branches. These changes don’t go into the current release branch but are kept for the main branch or a future release. 🔄🌟
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
Create from main/master if it’s a live, critical issue needing immediate attention. Create from release branch if it’s a release-specific fix that isn’t live yet.
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!!!!
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!!!
My vocabulary is not enough to Praise You....Thank you so much sir
😍😍😍
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. - Simplified by CloudNP9458. Thanks for another great lecture @Abhishek Brother. ❤
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
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
Excellent explanation
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!
Thank you sir....the way that you are explaining is understandable to anyone with no knowledge.
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!
Great Uber example, Explained well.
Thanks !!
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 🙂
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 😊
nice and easy explanation!
I understood branching strategy clearly thanq so much abhishek for you your efforts to make understand the concept of branching
Completed Day:10 Video and Practice also done.
Thanks Veeramalla garu
GK from NJ
Thanks a lot !!
Really good explanations. Thank you.
Beautiful Explanation 👍👍👍👍👍
Thanks and welcome
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
Learned something new about Git which I was unaware of until today.
Awesome
Hi Abhishek veeramalla I had just started exploring your playlist, you are simply an amazing mentor
Thanks a ton
Completed day -10 successfully
Thank you so much for this video, got my concepts cleared related to branching strategy
Great to hear!
Thank you 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🌸
Wonderful explanation!! Truly thankful 👏
Glad it was helpful!
You are God of devops sir
❤️
Thank you Sir, I got the same question and explained exactly, though am working i didnt had this much idea,it is realy helpfull..
Hi Abhishek excellent session. Thanks for brushing up my git knowledge.
My pleasure
Thank you so much abhi sir, got the complete understanding of the concept.
Completed this Video on 29th June 2023.
❤️❤️
🙏🙏🙏❤ for ur dedication and teaching
It's my pleasure
Thanks a lot. your doing great job . I appreciate your efforts , I tell you bottom of my heart.👍👍
It's my pleasure
Awesome. Got this topic so easy.
Thank you Abhishek ❤
Thankyou for the stuff but if you have showed practically that will help a lot more to the people....TQS bro
Learnt a great and new info thanks @Abhishek❤❤❤❤
Great explanation Sir.
welcome
Thank you so much. The explanation is fantastic and helpful. You are gonna be my mentor..
Happy to hear that!
Thanks so much sir you’re doing a wonderful job
It's my pleasure
Content was really good 👍
Thanks
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
Day-10 Completed successfully :) and Thank you Abhishek :) .
Thanks a lot for making this video Sir. It was superb with real world examples ❤
Completed 10 days course.
Thank you Abhishek, it's very clear
You're most welcome
Thank You Sir! Learnt something new !
Glad to hear that!
This is pure gold
Most welcome !!
Superb, thank you
Welcome 😊
Thanks a lot. This is really good. I finally got it.
Glad it helped!
Super anna....Neet ga explain chesaru.
😍
Thanks Abhi.. Clearly understood 😊
My pleasure 😊
Thank you sir
Welcome
Thanks Bhai!
Go On.
Thanks
Thanks a lot. very well explained with examples.
awsome
Thank you ❤️
Very nice explanation Abhishek bro....Keep on rocking the knowledge sharing...my lovly kudos to u
Thanks a ton
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..
Hope that today it 'll be practical session of branching strategy.
Hope you enjoyed video
@@AbhishekVeeramalla yeah bro
Very Helpful!😍 Thank you So much
Thank you ^^
Awesome content, keep it up Abhishek...Love and respect from Pakistan.
😍
Thank you bro, Very helpful.
Thanks a lot
nice
Thanks
you r god of devops
❤️
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
Thanks
Thanks alot Upendra
great explanation .
Thanks ,its Clear concept.
Grateful😇 Thankyou Abhishek
I am watching from Noida Delhi ncr
Thanks
Day-10 done ✅️🙂
Keep Going..
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.
Thank you for your presentation. How about the testing branch to validate new features before deliverying to customers?
Awesome, got you. It's easy
Good explanation abhishek keep it up 👏👏
Thank you so much 😀
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
Great Explanation,Very easy to understand.How can we add tagging to release branches ?
Well explained 😊 thanks
My pleasure 😊
Awesome. Please share the videos with your friends
thaank 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 ❤️
#Day10 done
i completed this video abhishek
I think one more to add here we will have development branch where the developers will develop the code daily and when required they will merge the code to master branch. To sum up we will have Master Branch, Hot fix Branch, Development Branch, Feature Branch, Release Branch
Great video :)
Best
Hi , great explanation? Are you planning to do any playlist for developers as a beginner?
While listening to this, I got question in my mind like enhancements are released via release branch and what about Master?I stopped and was scrolling for relevant comments.After that resumed and got the answer at 15:03 😆
sir can you please explain the difference between trunk based and gitflow branching stratergies
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 🙏 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 !!
Good content brother, it will be very helpful if you privide notes{your content and interview question and answers} also .
Ok next time
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.
Your understanding is 99.999% correct ! 🤓
✨ Branching for Release:
When we create a release branch from the main branch (like "main" or "master"), it's a snapshot of the code planned for release 🚀. This branch should be as stable as possible.
🛠 Changes to Release Branch:
After creating the release branch, it should only get critical fixes or final tweaks for the release. No new features or big changes go here! ❌✨
🔄 New Development in Dev or Feature Branches:
All new features or improvements continue in "dev" or feature branches. These changes don’t go into the current release branch but are kept for the main branch or a future release. 🔄🌟
Jai Balayya Jai Mallayya
Haha
Like in feature branching strategy, what actually master branch is referencing to the tip of latest commit ?
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
great seesion, thank you. I have one query - In github should we need to create hotfix branch from release branch or master branch?
Release
Create from main/master if it’s a live, critical issue needing immediate attention.
Create from release branch if it’s a release-specific fix that isn’t live yet.
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
Abhishek,could you just show a practicals on merge and rebase.
For sure
you meant multi branching for microservices application according to your explanations. Right?
Hi @abhishek can you please update the github documentaion via github repo
❤