Hi Abhishek, Thank you so much for sharing the knowledge. But I got one doubt in the jenkins faulty application concept,as you told we have the roll back strategy ie is blue -green deployment in case of faulty application. My question is when you delete the application 34 after successful deployment of application 35, how will you direct the load to the application 34?
not after successful deployment after successful testing like we have HA load balancing and other testing scenarios is sucessful only we will remove the old version in our environment.
Hi Abhishek, in Multi branch setup like separate jobs for Dev,QA, Staging and Production servers, How do we ensure security among different branches. Thanks
Hi Sindhu, The only difference is that CICD pipeline for production and UAT have slightly different configurations w.r.t parameters and application configuration. The reason why we maintain different pipelines is to isolate the deployment process for multiple environments. You don't want a dev application to be deployed in production accidentally right ?
I practiced ci/cd with Terraform and git as repository,, could you please provide questions on this combination sir. Can I consider Terraform as ci/cd tool?
CICD can be anything not just source code in Java or Python. If you want to achieve CICD of infrastructure management then yes, you can consider Terraform as your CD tool. There is no real definition or toolset for CICD.
Hi as you explained regarding blue/green deployment if a new app is not working as expected then switch the load balancer to previous stable app.. do we need to maintain all the previous stable versions or only -1 version cause it takes computing power and storage and those are pay as you go services in cloud right.
Yes .. that's the downside of blue green .. only if you are not worried about the costs and if you want to go for a simple approach.. easy to configure and less time to revert to old state .. go for blue green
In the Blue green deployment, what happens to the users who are using version 34 and do not want version 35? is there a means for them to continue using version 34?
Great interview questions. Please drop other CICD tools interview Q& A for further ready to get DevOps jobs
Thank you so much for this. Your content is pure gold 👌🏼👏🏻
Thanks alot
Thank you so much Abhishek ,this is really good all 5 questions are very important from interview perspective and you have explained well.
1. How to resolve broken pipeline issue in Jenkins?
2. How to control resource usage in Kubernetes?
Can you please explain if possible!!
both of them are very lengthy questions. I will try to answer them as part of the trouble shooting videos.
@@AbhishekVeeramalla sure please add in the upcoming session if possible. Thank you
Nice Explanation Sir
Thanks and welcome
Good job sit and thank you🙏
Welcome
Great one
Thanks
Most helpful....
Thanks Reyanshi
👍👍👍
Thanks a lot
Hi Abhishek,
Thank you so much for sharing the knowledge. But I got one doubt in the jenkins faulty application concept,as you told we have the roll back strategy ie is blue -green deployment in case of faulty application.
My question is when you delete the application 34 after successful deployment of application 35, how will you direct the load to the application 34?
not after successful deployment after successful testing like we have HA load balancing and other testing scenarios is sucessful only we will remove the old version in our environment.
I can deny with the usage of CI as jenkins is widely used more. i see flexible is gitops or azure devops and writing pipelines
Agree. +1 for GitOps. I myself is an ArgoCD member and OpenSource contributor for GitOps.
How jenkins job cleaning process going on? Do u do it manually or u have pipeline set up? For how long u keep the jobs before cleaning etc etc
Very helpful bro
Thanks Mario
thank you
🙏
make a video atleast 30 minutes bro
yor are doing great job
Sure, I will try
iam thankful to you immensely on this video abisheck is there any way to connect with you apart from you tube channel
You can reach me on LinkedIn
Hi Abhishek,
in Multi branch setup like separate jobs for Dev,QA, Staging and Production servers, How do we ensure security among different branches.
Thanks
Noted. I will try to explain that
.Jenkins folder backup
@abhishek sir how to generate two or three artifact once using Jenkins pipeline . this questions interviewer asked me
Thanks for the question.. I will try bring such things in the course
@@AbhishekVeeramalla thanku sir
You can use wild card pattern to same any number of artifacts, For example All Jars - **/*.jar All War - **/*.war and so on. **/ means Any directory.
May i know the difference in cicd pipelines which we use it on different environments like dev testing QA UAT?
Hi Sindhu, The only difference is that CICD pipeline for production and UAT have slightly different configurations w.r.t parameters and application configuration. The reason why we maintain different pipelines is to isolate the deployment process for multiple environments. You don't want a dev application to be deployed in production accidentally right ?
Thank you so much
I practiced ci/cd with Terraform and git as repository,, could you please provide questions on this combination sir.
Can I consider Terraform as ci/cd tool?
CICD can be anything not just source code in Java or Python. If you want to achieve CICD of infrastructure management then yes, you can consider Terraform as your CD tool.
There is no real definition or toolset for CICD.
However, I see a problem with managing Terraform statefile in Git. Please watch my video on problems with terraform
Can I say i have used "Azure devops tool " for continuous integration/deployment? ,in your video you have used Jenkins.
For sure
every cloud provider have his own ci/cd services (at least 3 top), Jenkins is cloud agnostic and popular for his open source framework.
Thanks for answering Joan
Sir g will there be questions like this in the intern-interview as well?
yes
running smoke at 1st question means sir ?
Hi as you explained regarding blue/green deployment if a new app is not working as expected then switch the load balancer to previous stable app.. do we need to maintain all the previous stable versions or only -1 version cause it takes computing power and storage and those are pay as you go services in cloud right.
Yes .. that's the downside of blue green .. only if you are not worried about the costs and if you want to go for a simple approach.. easy to configure and less time to revert to old state .. go for blue green
In the Blue green deployment, what happens to the users who are using version 34 and do not want version 35? is there a means for them to continue using version 34?
Do you do Devops classes?
Nothing at the moment
Can't we use scale-in / scale-out strategy for Canary deployment?
It's better to use kubernetes
Hi bro, i want to do the one real-time project can you help me in this?
Very very soon.
How to rollback from Jenkins
Sure, I will try to make a video on that
Bro how do I contact you
I am available on LinkedIn