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 UA-cam trust me.
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 😊
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
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 👏👏🙏🙏🙏🙏🙏🙏
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 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🌸
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 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.
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 😆
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
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
Master holds production-ready code. Feature branches are for new functionality. Develop is where features are integrated and actively developed. Release branches prepare code for the next version release, stabilizing and finalizing the code. Hotfix branches are used for urgent fixes in production, then merged into master and develop.
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 UA-cam trust me.
Awesome. Please share the videos with your friends
Thanks
Thanks alot Upendra
Your the torchbearer for those who stucked and with confusion with develop learning, thanks a lot please keep it up for upcoming too
My vocabulary is not enough to Praise You....Thank you so much sir
😍😍😍
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
Great Uber example, Explained well.
Thanks !!
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.
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 Abhishek excellent session. Thanks for brushing up my git knowledge.
My pleasure
Learned something new about Git which I was unaware of until today.
Awesome
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
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!
Hi Abhishek veeramalla I had just started exploring your playlist, you are simply an amazing mentor
Thanks a ton
Really good explanations. Thank you.
Thank you so much for this video, got my concepts cleared related to branching strategy
Great to hear!
Completed Day:10 Video and Practice also done.
Thanks Veeramalla garu
GK from NJ
Thanks a lot !!
Wonderful explanation!! Truly thankful 👏
Glad it was helpful!
Beautiful Explanation 👍👍👍👍👍
Thanks and welcome
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 🙂
Very nice explanation Abhishek bro....Keep on rocking the knowledge sharing...my lovly kudos to u
Thanks a ton
Content was really good 👍
Thanks
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. ❤
I understood branching strategy clearly thanq so much abhishek for you your efforts to make understand the concept of branching
Thanks so much sir you’re doing a wonderful job
It's my pleasure
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🌸
Completed day -10 successfully
Thanks a lot. This is really good. I finally got it.
Glad it helped!
nice and easy explanation!
Super anna....Neet ga explain chesaru.
😍
Thank you so much. The explanation is fantastic and helpful. You are gonna be my mentor..
Happy to hear that!
Thank You Sir! Learnt something new !
Glad to hear that!
Excellent explanation
Thank you Abhishek, it's very clear
You're most welcome
🙏🙏🙏❤ for ur dedication and teaching
It's my pleasure
Thank you Abhishek 🙏
You are God of devops sir
❤️
Thank you so much abhi sir, got the complete understanding of the concept.
Completed this Video on 29th June 2023.
❤️❤️
Great explanation Sir.
welcome
Thanks Abhi.. Clearly understood 😊
My pleasure 😊
Awesome content, keep it up Abhishek...Love and respect from Pakistan.
😍
Thanks a lot. very well explained with examples.
Learnt a great and new info thanks @Abhishek❤❤❤❤
Thankyou for the stuff but if you have showed practically that will help a lot more to the people....TQS bro
Thank you Sir, I got the same question and explained exactly, though am working i didnt had this much idea,it is realy helpfull..
Awesome. Got this topic so easy.
Thank you Abhishek ❤
Thanks a lot for making this video Sir. It was superb with real world examples ❤
Very Helpful!😍 Thank you So much
Day-10 Completed successfully :) and Thank you Abhishek :) .
Thanks Bhai!
Go On.
Thanks
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. your doing great job . I appreciate your efforts , I tell you bottom of my heart.👍👍
It's my pleasure
Good explanation abhishek keep it up 👏👏
Thank you so much 😀
Thank you bro, Very helpful.
Thanks a lot
Hope that today it 'll be practical session of branching strategy.
Hope you enjoyed video
@@AbhishekVeeramalla yeah bro
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 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..
This is pure gold
Most welcome !!
Grateful😇 Thankyou Abhishek
Thanks ,its Clear concept.
good
Thank you sir
Welcome
Awesome, got you. It's easy
Completed 10 days course.
you r god of devops
❤️
great explanation .
Thank you ^^
Well explained 😊 thanks
My pleasure 😊
Awesome. Please share the videos with your friends
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
I am watching from Noida Delhi ncr
Thanks
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.
awsome
Thank you ❤️
thaank you
💐
Day-10 done ✅️🙂
Keep Going..
Thank you for your presentation. How about the testing branch to validate new features before deliverying to customers?
nice
Thanks
Great video :)
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 😆
i completed this video 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
Eureka is superior than those
@@Cloudnp9458 then y u r watching here
Thanks Shiva ❤️
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 Explanation,Very easy to understand.How can we add tagging to release branches ?
sir can you please explain the difference between trunk based and gitflow branching stratergies
Best
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
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
Hi , great explanation? Are you planning to do any playlist for developers as a beginner?
Abhishek,could you just show a practicals on merge and rebase.
For sure
Hi Abhishek, what about develop branch ..could you please explain in brief?
Hi @abhishek can you please update the github documentaion via github repo
hi bro if possible can you please do Realtime hands-on videos so its help full to us
Ya sure .. will do more
Hello All viewers,
Please dont mind to mention interview questions that you might have been asked ,These questions can help others.
#Day10 done
@abhishek, wondering long lived, short lived branches. long lived branches are master/main branch and development branch, can you explain difference
Like in feature branching strategy, what actually master branch is referencing to the tip of latest commit ?
what is difference in feature and release branch ?
Please watch the complete video. It is explained
Master holds production-ready code.
Feature branches are for new functionality.
Develop is where features are integrated and actively developed.
Release branches prepare code for the next version release, stabilizing and finalizing the code.
Hotfix branches are used for urgent fixes in production, then merged into master and develop.