auto commit

Signed-off-by: Song Song Li <[email protected]>
songleo · Dec 28, 2023 · 0fef5b1 · 0fef5b1
1 parent 6184a83
commit 0fef5b1
Show file tree

Hide file tree

Showing 2 changed files with 1 addition and 27 deletions.
diff --git a/...s/2023-12-28-software-delivery-process.md → ...3-12-28-software-delivery-process-tips.md b/...s/2023-12-28-software-delivery-process.md → ...3-12-28-software-delivery-process-tips.md
@@ -1,6 +1,6 @@
 ---
 layout: post
-title: 软件交付流程
+title: 软件交付流程tips
 date: 2023-12-28 00:12:05
 ---
 

diff --git a/_posts/github.md b/_posts/github.md
@@ -12,29 +12,3 @@ date: 2023-03-13 00:12:05
     - https://media.licdn.com/dms/image/D4E22AQFhtND12RqLKw/feedshare-shrink_800/0/1700066713756?e=1703116800&v=beta&t=419amzm57vXc2A2RW9mk3N94gDRf378O9e-gjvimAaQ
     - https://chat.openai.com/c/a8043da3-cae8-4ee0-a080-a629387fecb2
 - https://media.licdn.com/dms/image/D5622AQFS4YY_9lYTdQ/feedshare-shrink_1280/0/1697444954712?e=1700092800&v=beta&t=2WdfeRRgUrsokXiFtxHP3xY9Ib7AmLj3qksfpZ9hCYw
-
-- https://media.licdn.com/dms/image/D4E22AQHoYMZjS4rWXQ/feedshare-shrink_1280/0/1697298328213?e=1700697600&v=beta&t=GNPmaqi1XWcFjAqwBCXFxBKox1pfQZOcuk7hD7NJpoo
-
-```
-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.
-```