Комментарии:
Grateful😇 Thankyou Abhishek
ОтветитьWhat if there is Prod issue on Release Branch, and Master also has same code ?
Ответить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
Completed Day:10 Video and Practice also done.
Thanks Veeramalla garu
GK from NJ
what is difference in feature and release branch ?
Ответить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?
ОтветитьSuper anna....Neet ga explain chesaru.
Ответитьso I have a doubt, so will release branches eventually merge into master branch? and is release branch is extracted from master branch or feature branch?Thanks
Ответитьbro after our work is completed you said we can delete our branch.
if in case we get some medification after deleting the branch we need to create a new branch from master branch and do changes 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?
ОтветитьHi sir, after adding to main branch why we are deleting feature branch everytime, is it necessary to delete it?
Ответитьfrom where we have to create a hot fix branch ?? is it from main branch or release branch ??
ОтветитьHi Abhishek, hotfix branch created from which branch ? is it from Release branch or Master branch ?
Ответить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🌸
ОтветитьGreat Uber example, Explained well.
ОтветитьHi Abhishek, how can specific people merge their changes directly to the master branch rather than raising pull request. This was the question asked in the interview. Could you please answer this.
ОтветитьHi Abhishek ,
I have a doubt,
Now Main /Master branch is running ,if customer come and request us to change something we will create the feature branch and work & merge with master branch code(release branch V2)
Again if customer come and request us to change something we will create another one feature branch and work & merge with master branch code .
My question is whenever we change something in feature branch and merge with master branch, will it automatically update & release or until /unless we create release branch (V3) ,will it save as incremental code with master branch? I hope my question is clear...
Hi sir...
Very Good Evening, I am a fresher...
I completed my graduation in the year of 2022. I did AzureDevOps and Azure(cloud) course for 3 months.
Is AzureDevOps good to start my career sir. Any Suggestions from your side sir.
Very Helpful!😍 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 😊
ОтветитьDay-10 done ✅️🙂
ОтветитьThankyou for the stuff but if you have showed practically that will help a lot more to the people....TQS bro
Ответитьhey @AbhishekVeeramalla , how can i open my git terminal like you?
ОтветитьHello Abhishek, thanks for the video. Great content as usual. I have a question though, Is it mandatory for every hotfix branch to merge into master, sometimes release1.0 branch could be behind main branch by some commits and the fix might probably be only relevant to the hotfix branch, in this case(if it exists) does the hotfix branch still gets to master/main?
ОтветитьThanks so much sir you’re doing a wonderful job
ОтветитьThanks a lot. This is really good. I finally got it.
ОтветитьThank you sir
ОтветитьHi Abhishek, Can I use the same branching strategy for windows application? Generally we follow branching strategies like dev,qa,pre-prod and prod. Let's say qa is our release branch which is going to customers? Then what is the use of pre-prod and prod(master)?
ОтветитьThank You Sir! Learnt something new !
ОтветитьAwesome content, keep it up Abhishek...Love and respect from Pakistan.
Ответитьhot-fix branch is created for quick bug fixes or adding quick features ,and then it merge into a release and master branch to kept it up to date .....am i right sir....plzz reply to me sir
ОтветитьThank you so much abhi sir, got the complete understanding of the concept.
Completed this Video on 29th June 2023.
This channel is Gem for Devops mastering, I appreciate your efforts, Good work!!!
ОтветитьLike in feature branching strategy, what actually master branch is referencing to the tip of latest commit ?
ОтветитьHello Abhishek,
I was suggested your videos by one of my friends and trust me I have never seen a channel with such information with real-time examples. Thanks a lot.
I have got a question here, let us assume
we have cloned our feature branch out of master. Started working on it.
meanwhile, Another Developer committed his changes, now when I tried committing my changes I have seen merge conflicts. Can you put some insights on how to deal with this situation?
I thought master/main is a production branch for customers, but now I understand it just updated code maintaining branch,
Release branch is the production branch for customers.
Am I correct?
By the way Thanks for wonderful series, I will complete the entire series soon❤
Hi Abhishek what is the main difference between feature & release branch ? I think release branch will be used when user wants some functionality to get deliver in some particular period of month ?
Ответить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.
ОтветитьHi Abhishek..your videos are awesome..i have one question here..when we use Jenkins and while checkout SCM we should use the release branch right to deploy the application into production
Ответить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
Learned something new about Git which I was unaware of until today.
ОтветитьThank you bro, Very helpful.
Ответить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
ОтветитьQuick question, what about staging, testing or dev branches. Are they also part of these strategy as well for open source projects like kubernetes, docker or jenkins. As my current organization follows this strategy feature branch => dev branch => alpha branch => beta branch => main/release branch and i think this process has some problems.
Ответитьnice
Ответитьhi bro if possible can you please do Realtime hands-on videos so its help full to us
Ответитьyou r god of devops
ОтветитьI'm little bit confused with branching strategy bcz someone is saying like release branch is fixed and what about development branch when it is using ?
Ответитьsir, Actually in git for every new version release
Did you create a new release branch from main branch?
Great explanation Sir.
Ответить