How Companies Ship Code to Production

 Referred Link - 

https://www.linkedin.com/posts/aaj5_softwaredevelopment-devops-ci-activity-7209397051787300864-bdQD

How Companies Ship Code to Production: A Step-by-Step Guide

In today's fast-paced tech world, shipping code efficiently and reliably is critical for delivering value to customers. Here's a visual breakdown of the process many companies follow to ensure seamless code deployment from planning to production:

Plan
1️⃣ Create Stories: The Product Owner creates user stories in Jira, outlining the new features and requirements.
2️⃣ Take User Stories: Developers take the user stories and prepare to turn them into code.

Development
3️⃣ Commit Code to Git: Developers write code and commit it to a version control system like GitHub.
4️⃣ Build: Using tools like Jenkins, JUnit, JaCoCo, and SonarQube, the code is built and tested. Successful builds are stored in JFrog Artifactory.

Build & Package
5️⃣ Deploy to Dev Environment: The built code is deployed to a development environment using Docker.
6️⃣ Deploy Feature to QA Environment: The code is moved to the QA environment for further testing.

Test
7️⃣ QA Testing: The QA team conducts various tests, including regression and performance testing.
8️⃣ Deploy Feature to UAT Environment: After passing QA, the code is deployed to the UAT environment for final validation.

Release
9️⃣ UAT Testing: Final user acceptance testing is performed to ensure everything works as expected.
🔟 Deploy Feature to Prod Environment: Once approved, the code is deployed to the production environment.
1️⃣1️⃣ Monitoring and Alerting: SRE (Site Reliability Engineering) teams monitor the production environment using tools like ELK Stack, Prometheus, and Skywalking to ensure smooth operation and quick issue resolution.