How do companies ship code to production? . . -- Subscribe to our weekly newsletter to get a Free System Design PDF (158 pages): https://lnkd.in/g9wAgcke -- The diagram below illustrates the typical workflow. Step 1: The process starts with a product owner creating user stories based on requirements. Step 2: The dev team picks up the user stories from the backlog and puts them into a sprint for a two-week dev cycle. Step 3: The developers commit source code into the code repository Git. Step 4: A build is triggered in Jenkins. The source code must pass unit tests, code coverage threshold, and gates in SonarQube. Step 5: Once the build is successful, the build is stored in artifactory. Then the build is deployed into the dev environment. Step 6: There might be multiple dev teams working on different features. The features need to be tested independently, so they are deployed to QA1 and QA2. Step 7: The QA team picks up the new QA environments and performs QA testing, regression testing, and performance testing. Steps 8: Once the QA builds pass the QA team’s verification, they are deployed to the UAT environment. Step 9: If the UAT testing is successful, the builds become release candidates and will be deployed to the production environment on schedule. Step 10: SRE (Site Reliability Engineering) team is responsible for prod monitoring. Over to you: what's your company's release process look like? -- Subscribe to our weekly newsletter so you won't miss it: https://bit.ly/3KCnWXq #systemdesign #coding #interviewtips .
I have a question: is there a metric like this: edit a line and put this code to production. Measure the speed 1 to the test bench, 2 to the production. If there it is i want to see statistics for it and how it’s related to type of companythat has it
You guys test?
Great ilustration but FMPOV is a old school way.
Here’s what our company's release process looks like. We use Builder for building, testing and packaging our software, and Release automates complex deployments to Kubernetes or to any cloud platform. (We can build once and deploy anywhere). If you’re curious how robust? We have fortune 500 clients continuously deploying several times a day to production without downtime using the same platform. Builder & Release are applications inside the AuditDeploy platform. https://www.linkedin.com/posts/stabler_deploymentautomation-continuousdeployment-activity-7168699412397895681-fMiZ?utm_source=share&utm_medium=member_ios
I follow same process. Some specific inputs about step, "A build is triggered in Jenkins. The source code must pass unit tests, code coverage threshold, and gates in SonarQube.", a.) When developer writes code with TDD approach, there is good chance to get Code coverage >= 80%. b.) If developer follows good code practices then there will be less Code Smells from SonarQube gate.
I posit that these days Docker also plays a large role in the development phase. There are many companies using containerization as an approach to better SDLC even if they're not shipping containers to production. I'd also add that thanks to tools like Testcontainers there's a full end-to-end integration testing phase that happens in the dev cycle.
What tool you use for creating this presentation?
Can you please help me how we can release multi node cluster production release using docker. I know using k8s
Senior QA analyst / Senior Business Analyst
5moFailed at first swim lane , none of the product owner is smart to write user stories so they hire BA, 90% of BAs not experienced they just do requirements gathering no analysis so our starting or planning starts with vague and incomplete requirements or user stories and that goes till release. Only smart ,experienced and dedicated team can deliver what is required for business. No matter what process , softwares or methodology we use. Static testing is missing in plan phase which is critical, involving QA in later phase has made it more like waterfall model. Another most important thing is IT projects lack technical project managers which is big pain for the team and disaster for the project, all they seem to do is assignment of work with unrealistic deadlines and expecting results without knowing through the intricacies of project requirements in detail up to the level of one single vague requirement which is causing so much delay and even it has been implemented its still there to haunt to QA resource to get understanding of it and coming of with correct and right number of test cases . A bad or inexperienced project manager is pain the neck for the whole team. Development technical lead is better alternative.