How to Explain a DevOps Project | How to Explain Project in Interview | LetsTalkDevOps

[@mudassirsyed8655]

The best video on KZbin on project explanation. Thank you for this great content

[@LogicOpsLab]

Glad it was helpful

[@hrithikbhardwaj3689]

Seriously you are doing great . I was searching this type of video from last 2 month no one will explain the real time environment things . Thanks

[@LogicOpsLab]

Means a lot, Hrithik

[@SnehithKurupathi-l2h]

Seriously Man this video so amazing. I was searching for a content like this to answer the question explain about the project. Many thanks to you

[@LogicOpsLab]

Glad I could help! This means a lot to me.

[@KESHAVBISHT-bj5vz]

Amazing. Was searching for something like this.

[@LogicOpsLab]

Glad I could help

[@hassanmir5309]

This explanation is awesome, I really appreciate your handwork and efforts you have put. I requested you to please make a video of end-to-end application stack used in DevOps archtitecture.

[@LogicOpsLab]

Means a lot, thanks for the feedback. Sure, I will make one.

[@AshranBaig]

A very well explained youtube video for a project, I am giving interviews after a very long time being off project. It was a good revision and will definitely help in giving interviews. Keep making great content...All the best.

[@LogicOpsLab]

This made my day. Thanks a lot, mate.

[@rawdevops10]

I understood about artifacts after this. Thank you so much, Sir.

[@LogicOpsLab]

Means a lot, mate.

[@harikaallam2406]

Thanks for this detailed explanation Ravish!

[@LogicOpsLab]

Thank you! Best wishes!

[@devopsjockey]

Love from kerala your video are worth and waiting for many

[@LogicOpsLab]

Made my day, thanks a lot!

[@johnbobonline501]

Very good explanation of project ….i love it …you are good

[@LogicOpsLab]

Means a lot, mate. Do share with other folks.

[@janakiramang9185]

Good explanation :)

[@LogicOpsLab]

Appreciate your feedback. Thank you!

[@narsinghsaini3626]

Good Explanation. Thanks.

[@LogicOpsLab]

Appreciate it. Thanks.

[@anubhabisht8480]

One of the best videos. ❤

[@LogicOpsLab]

Best video this side of the internet! Just kidding, but I appreciate the love!

[@anjalishende662]

Hello Sir, can you explain when the release branch was created any release pipeline triggers for it and if yes if we get issues do that get fix in the release branch itself ? the release pipeline runs on which environment ?

[@gangadharb2406]

you rock it! thank you for your effort!

[@LogicOpsLab]

Means a lot

[@thetirkitguy-viveknawle5713]

Amazingly explained ravish bhai ❤

[@LogicOpsLab]

Thanks a lot, Vivek

[@nazgulm4882]

Thank you for the great explanation.

[@LogicOpsLab]

Thanks for the feedback 🙏🏻

[@NaveenKumar-vy2ug]

Hi Ravish, as you told in the video that Jenkins will fetch the code, sonarcube scanning,build,test, then push to the artifact, then deploy to the different environment like dev, qa, staging and prod. my question is how the artifacts get trigger to get deploy into theses stages, how the flow take place. example If artifact/Image get deploy into dev environment after the testing by dev team how QA , staging and prod environment get trigger? to deploy in each environment how the manager approval process take place what is the flow.. please explain this. I am having devops interview on Monday.🙏🙏

[@LogicOpsLab]

Here's a general overview of how this process might work: 1) Development Environment: Developers write and test code in their local development environments. Once satisfied, they commit their code to a version control system (e.g., Git). Before pushing changes forward, automated testing can also be conducted in the development environment. 2) Continuous Integration (CI) Pipeline: The committed code triggers an automated CI/CD pipeline. The pipeline compiles/builds the code runs unit tests and generates an artifact (e.g., Docker image, executable, etc.). If the tests pass, the pipeline produces a "build artifact" ready for deployment. 3) Quality Assurance (QA) Environment: The build artifact is automatically deployed to the QA environment. Automated integration tests, regression tests, and other QA processes are performed in this environment. The artifact can be promoted to the next stage if the tests are successful. 4) Staging Environment: The artifact is automatically deployed to the staging environment, which should closely resemble the production environment. More extensive testing, including performance testing and user acceptance testing, can be performed here. If the artifact passes all tests, it's ready for production. 5) At this point, some organizations introduce a manual approval step before deploying to production. This is often done for risk mitigation and to ensure that critical changes are reviewed before going live. Managers or designated individuals receive notifications about the pending deployment. They review the changes, assess potential risks, and decide whether to approve or reject the deployment to production. 6) Production Environment: Once the manager approves, the artifact is automatically deployed to the production environment. Depending on the organization's practices, this deployment can happen instantly or during a scheduled maintenance window. Continuous monitoring and automated rollback mechanisms should be in place in case any issues arise after deployment. It's important to note that the specifics of this process can vary widely depending on the organization, the tools and technologies in use, and the specific requirements of the application being deployed. The key principles are automation, consistency, and thorough testing at each stage to ensure that code changes move through the pipeline reliably and without causing disruptions in the production environment.

[@LogicOpsLab]

In short, dev to qa promotion is QA's responsibility. QA to production anyone from a senior perspective can promote. It is mostly a team. The production deployment happens in front of everyone. The DevOps/PO leads are the ones monitoring it.

[@NaveenKumar-vy2ug]

@@LogicOpsLab thank you sir.. As of my knowledge, automatic deployment from 1 environment to other environment is take place by jenkins webhook right? example suppose we have 4 branch in git hub like dev, qa, staging, prod.. when developer push the code to git hub ,with a help of webhook jenkins will fetch the code then automated build, test, deployment to dev environemnt take place,, after that when code merge to the qa branch, web hook will trigger code to jenkins then same step will take place as earlier then deployment to QA environment, then same thing for staging and production environment... Am I correct? In shorts, automatic deployment from dev to qa, qa to staging, staging to production is happen with a help of webhook trigger after merge with dev to wq, qa to stage, stage to prod branches in git hub, Am I correct? please help me on this If Iam wrong then on what mechanism automatic deployment between different env take place? please help me on this🙏

[@LogicOpsLab]

@@NaveenKumar-vy2ug Automatic Deployment can be done on the basis of a "Trigger". The right word is Trigger over here. Now, this Trigger can work differently in different tools. You can use it using a webhook, you can manually do it in Azure DevOps, and other CI tools.

[@NaveenKumar-vy2ug]

thank you sir@@LogicOpsLab

[@pranaykiran.p]

Thanks for Very good explanation bro

[@LogicOpsLab]

Thanks and welcome

[@rahulgedela8208]

Amazing session. Easily explained and summarized a project. Thank ypu for this🙂 In interviews, we can showcase this with whoch branching strategy? Feature, Task & Release?

[@LogicOpsLab]

It totally depends on you. Choose the one that helps you explaining it better.

[@thanvikamadhala-ip7kg]

Very helpful video

[@LogicOpsLab]

Thanks a lot.

[@sivadurgasairamb4097]

Greetings of the day, Thanks for good explaining about the process... please list out the issues or the type of errors occur in each each environment like dev, QA, uat, prod. will help us alot to answer in interviews..... please make a video or document so that will be more useful for us.. TIA... Happy learning😀 🎧

[@LogicOpsLab]

Sure thing.

[@user-dj7xb7dr2m]

Very helpful 🙏🏻

[@LogicOpsLab]

Thanks for the support

[@sourabh4834]

thanks you so much for this videos.. i have been searching for this kind of videos . great job helped me..

[@LogicOpsLab]

Glad to hear that

[@sourabh4834]

@@LogicOpsLab could you please tell what happens in deployment..

[@sourabh4834]

How to deploy to dev qa uat n pro environment

[@LogicOpsLab]

@@sourabh4834 Deployment means the application is now fully functional and is ready to be consumed by everyone. Every tool has a separate process for the deployment but the end result is the same.

[@sourabh4834]

Can i say for dev qa was running on Tomcat so i was deploying to Tomcat... The. For the production deployment happening through Kubernetes

[@akashzakde8160]

Thank you so much Ravish 🥰

[@LogicOpsLab]

Glad I could help you :)

[@touqirzams589]

you are kind of farishta for me,, in the form of human 🙏

[@LogicOpsLab]

Too kind of you 🙏🏻

[@figh761]

Could you please explain a GCP devops project wit challenges you faced.

[@LogicOpsLab]

Will make a video on it

[@crickettv5555]

great one

[@LogicOpsLab]

Thanks for all the support.

[@k_shaw9161]

Thanks for explaining this so well. Will add a few more things to it and use it as a base

[@LogicOpsLab]

Glad you liked it

[@SubhashreeDhal-l2y]

Insightful video, However, could you please let me know how application code branch and infrastructure branches are integrated? CI/Cd platform like GitHub action . i am aware of calling and called concept of GitHub workflow just wanted to know every time a developer pushes a code or any changes in the code, the corresponding workflow runs right (like an event driven pipelines) and it deployed to dev environment, so my question is every time DEV environment is dynamically created or all the environments are already there

[@LogicOpsLab]

Creation of environments in a one time process. You just create an environment one time and use it forever, unless you nuke/destroy it. Also, however the deployments happens 'n' number of times.

[@maheshnayak7631]

Could you please make a video with azure cicd pipeline and deploy with target environment web app

[@LogicOpsLab]

Sure, will put it in a week or so.

[@anantsolanki9471]

Hi Ravish Yr videos are very useful. But in reality there is very different scenario.i cleared first round in two big MNCs. But i was rejected in both interview in second round Though i clearly explained them .and gave 90 percent of right technical answers . They just want that person should work in same tech stack. They are least concerned about work distribution and yr current project.

[@LogicOpsLab]

Thanks for the feedback, Anant. Appreciate it. Try thinking it this way, if you are working in the same stack that you were working in the previous company, where is the margin to learn? In my opinion, you should join a company with 65-80% overlap. Otherwise, you are doing the same thing and this is penny wise, pound foolish. Next time, ask them for feedback. I assume there would be some non-negotiable technology and if you do not answer that, you will be rejected. Always know about the JD, what are the "Good to Have" and what are "Must Have". Best wishes, mate.

[@anantsolanki9471]

@@LogicOpsLab -Yes thats what i asked them , they rejected me just bcoz in my past company i did not got opportunity to work on Azure data bricks as hand on. many company's are copy pasting in sharing the JDS.

[@LogicOpsLab]

@@anantsolanki9471 True! I feel you but I think you just dodged a bullet. There are better opportunities waiting for you. Your personal growth matters a lot, you are not a robot who will do the same thing again and again. Wish you the best, mate.

[@anantsolanki9471]

​@@LogicOpsLab -Thanks Ravish, yr videos help us a lot in learning in field of DevOps.

[@LogicOpsLab]

@@anantsolanki9471 Keep growing, mate!

[@SunilKumar-zw4xs]

Very Good and Informative, but missed hotfix branching from the release/live branch. Thanks for your time

[@LogicOpsLab]

Thanks for the suggestion, mate. But, discussing branching strategies would've made a video longer. I have created a separate video for the same.

[@taknevydder]

Hi Ravish, I have doubt. After dev pushes the code into SCM, devops eng makes sure that artifact is built and deployed into different environments. How do QA team test the code? Do they run tests on artifact's? cause once you create artifact you deploy the application right. Where exactly or in which step/stage ? Or on what exactly are testers testing the code? And where does a devops engineer come in between development and qa?

[@LogicOpsLab]

Thanks for your question, Venkat. So, once the code is deployed In Dev, the developers do the initial testing. Once they're okay, the code is promoted to the Staging / QA environment. That's the time the QA folks test on the respective environment. It depends what type application it is, if it's a web app, the testing could be Selenium. There are other several testing frameworks. Api testing, manual testing, etc DevOps folks are needed to promote the build from Dev to QA or to any higher environment. The process differed company to company.

[@taknevydder]

@@LogicOpsLab Thanks really appreciate and also Ravish I have another doubt. Once is build is successful and deployed into QA env. Do the testers create a new branch in the SCM and work on it? If all the tests are successful, they do a pull request to which branch ? Master or staging ?

[@LogicOpsLab]

Testers don't create a new branch for testing unless there is a special case of writing new test cases. Even then they test their branch first, merged it to Dev, then it gets merged to higher branches.

[@taknevydder]

@@LogicOpsLab OP bro. Thanks for replying immediately. This video really did help me.

[@LogicOpsLab]

Glad it was helpful. Do like and share with your friends.@@taknevydder

[@swapnilsonawane1858]

Hi Just have a quations In every env do we have Jenkins pipeline And if yes how many pipeline we need to create and how many env Can you please reply this quations

[@LogicOpsLab]

Do we have a Jenkins pipeline for every environment? It depends on the structure and requirements of your project, but typically, you would have separate pipelines for different environments like development, staging, and production. Each pipeline can handle environment-specific tasks such as deploying the application, running tests, or performing other environment-dependent operations. How many pipelines do we need to create? The number of Jenkins pipelines you need depends on your project structure and deployment strategy. Generally, you may have: A build pipeline that compiles code, runs tests, and builds artifacts (e.g., JAR, ZIP, or Docker images). A deployment pipeline for each environment (e.g., dev, staging, production), which deploys the artifact to the respective environment. If you have microservices, you may need a pipeline for each service. How many environments are needed? Common practice involves the following environments: Development (dev): For initial testing by developers. Testing/QA (staging): For quality assurance testing. Production (prod): The live environment used by end users. Some organizations also include environments like pre-production or UAT (User Acceptance Testing) depending on their processes.

[@vinayaksalunkhe2875]

Hi Ravish, Thanks for the video. It is good. I have one question. @22 min 16 sec you said it is tested and pushed in dev environment by developers. Do you mean to say dev team also has web interface for website (similar to prod) where they check all functionality related to website or app?

[@LogicOpsLab]

A DevOps will create a Dev environment for the developers. This is done so that the developers can test how their code will look like when it will be promoted to higher environments. It can be done two ways, either they can push their code and the build starts automatically or they can manually trigger a build.

[@vinayaksalunkhe2875]

Sorry but still not clear. I am asking, if my code (devloped code by dev) is for website or for application. Then that website is available for devloper on other test URL or dev URL? To check their implementation is reflecting correct changes on website or not?

[@LogicOpsLab]

@@vinayaksalunkhe2875 It would be available on Dev URL. Every environment MUST have a separate URL. If it is a VM then the application/website has to be exposed through an IP address or a DNS name. If it is a web service, then a URL will be there for Developer testing. Therefore, for every environment, there MUST be a separate URL/Web Interface to test. I hope it makes sense now?

[@vinayaksalunkhe2875]

@@LogicOpsLab Thanks bro.... Now it's clear.

[@LogicOpsLab]

@@vinayaksalunkhe2875 You are welcome!

[@PRASANNAKUMAR-n4f]

for nodejs application what artifacts we get when build stage like for java .jar

[@LogicOpsLab]

For Node.js applications, the build process typically involves packaging the application into a distributable format, often as a Node Package Manager (npm) package. This package includes the application's source code, dependencies, and any necessary configuration files. Unlike Java applications, which are often packaged into JAR, WAR, or EAR files, Node.js applications are typically distributed as npm packages, which can be easily installed and managed using npm or Yarn.

[@vatsavaivillagelife6698]

Deployments any stages and step up environments and infrastructure should be taken care by everything DevOps Engineer?

[@LogicOpsLab]

More than 90% of the time, yes! Unless there is a separate team for infrastructure, which rarely happens.

[@vatsavaivillagelife6698]

Thankyou for sharing valuable information,

[@karthikbandi8518]

Hi, which tool they use to build C# and .Net applications?

[@LogicOpsLab]

Create a build pipeline that defines the steps needed to build your C# and .NET application. In the pipeline, you'll specify tasks such as restoring NuGet packages, building the solution, running tests, and possibly other steps depending on your project's requirements.

[@bin4mails]

Hello Sir, Apologies if my question is invalid, please educate me… Are the DEV,QA and PROD. the job of a Devops Engineer. and What about K8 and Docker Terraform and python in our project. please explain. Thanks in advance.

[@LogicOpsLab]

Hey! Thanks for the question. Yes, all of the tech you mentioned is a responsibility of a devops engineer. Personal Opinion - It can vary company to company but wherever I have worked till date, it has been always my responsibility.

[@NaveenKumar-vy2ug]

Hi , I have 1 doubt , sonar cube scanning is done before code build?

[@LogicOpsLab]

It is totally your call: 1) Scanning before - Useful to get the code coverage, if the code coverage is beyond what you have set up in the quality gates, then it's cool. Otherwise, fail the build. 2) After - After the code is successfully built, the SonarQube analysis is performed on the generated binary or package. This analysis checks for code quality, security vulnerabilities, code smells, and other metrics.

[@sheandmeandtravel]

@@LogicOpsLab thank you 🙏🙏

[@Christmasene]

How to answer Can u walk us through a project u made wider impact on department/organization, Your contrition to the project-for 3 years expereienced

[@LogicOpsLab]

Key Achievements: Highlight the key achievements and contributions you made. Focus on specific results, improvements, or impacts. Use quantifiable data when possible. For example: "I led a team that reduced deployment times by 40% through automation, resulting in a 20% reduction in operational costs." "I implemented a CI/CD pipeline that reduced the error rate by 60%, improving the overall reliability of the system." Challenges Faced: Mention any challenges or obstacles you encountered during the project. This shows that you can adapt and problem-solve. "We faced scalability issues, which I addressed by redesigning the architecture to handle 10 times the previous load." Lessons Learned: Share any lessons you learned during the project. Mention how these lessons could be applied to future projects. "One important lesson was the value of effective communication and documentation in complex projects. This experience has made me a better team player and communicator."

[@nil1473]

👌👌👌

[@LogicOpsLab]

😀

[@Jalal921]

how can we put this in resume for interview?

[@LogicOpsLab]

I have a few devops real time projects on my channel. Just check one of them, and put that in your resume. Explain it in this way.

[@jayeverything]

💯

[@LogicOpsLab]

Thank you

[@saravanarajan3327]

Hi iam not getting calls for devops job as a fresher can u help on it please

[@LogicOpsLab]

Check out my resume series and make changes accordingly. It will surely help you.

[@iamsohailsp]

Docker😢😢😢

[@LogicOpsLab]

What about it?

[@iamsohailsp]

@@LogicOpsLab interview on Docker please Rocky bhai 🤗

[@LogicOpsLab]

@@iamsohailsp Sure thing

[@subhrakantasahoo8075]

Hii Ravish, actually I am showing 3.5 yr fake experience in AWS devops, actually I want to know Which AWS Resources we want to study...I am totally confused (I know only Ec2,Lamda,Beanstack,Ebs,S3,Efs,storage gateway,VPC,IAM,Auto Scalling,Load Balancer,Cloud Formation,Cloud Front,Cloud Watch,Sqs,Ses,Sns,AWS Cost Optimization,Rout 53....This much) is this sufficient for if I am showing 3.5 Yr experience Plz help me Apart from I know All Devops Tool Git Ansible Teraform Docker K8 Maven Jenkins.I am totally confused with Aws Resources Plz help Me....

[@LogicOpsLab]

Please connect with me on LinkedIn

[@subhrakantasahoo8075]

Sir I am everytime following u but still u suggest me,is there another service required