現今網站發展科技突飛猛進，Web網頁也從1.0發展到3.0，從靜態網頁發展到智能服務反饋等處理，K公司客戶端也為符合使用者需求及便利性，皆以網頁應用系統開發，其網路的安全性更加重要。現行K公司內部使用技術大都為Java，其中部分專案程式設計師期望將專案盡速完成，K公司在沒有版本控管的年代，曾經有工程師同時修改同一支程式，以致於疏忽或導致程式碼沒有合併版本及覆蓋掉已經改好的程式導致更新部署上的疏漏問題。另一方面，K公司接受委外開發的網站系統越來越多，且客戶每年度變更或擴增需求也會有相對性的調整，於維運過程更新及佈署系統的更新頻率也增加，便會增加此類更新佈署狀況的風險。本論文提出以軟體開發維運持續整合與交付部署自動化方法論進行流程改善，希望在分析、開發階段程式碼的合併及佈署問題，減少軟體開發的時程要求。本研究將提出解決方案及測試過程說明

Today's website development technology is advancing by leaps and bounds, and web pages have also developed from 1.0 to 3.0, from static web pages to intelligent service feedback and other processing. In order to meet user needs and convenience, the clients of K Company are all developed with web application systems. safety is more important. At present, most of the internal technologies used by K Company are Java, and some of the project programmers hope to complete the project as soon as possible. In the era when K Company had no version control, there were engineers who modified the same program at the same time, so that they were negligent or caused the code to fail. Merging versions and overwriting the modified programs lead to omissions in update deployment. On the other hand, Company K accepts more and more website systems to be developed outsourced, and customers' annual changes or expansion requirements will also be adjusted accordingly, and the frequency of updating and deploying systems in the maintenance and operation process will also increase. would increase the risk of such update deployments. This paper proposes to improve the process by using the continuous integration of software development, maintenance and operation and automation of delivery and deployment, hoping to reduce the time schedule requirements of software development in the analysis and development phase of code merging and deployment. This study will propose a solution and a description of the testing process.

[1] DevOps， https://www.iiiDevOps.org/
[2] Jenkins， https://www.jenkins.io/zh/
[3] 維基百科， https://zh.m.wikipedia.org/zh-tw/DevOps
[4] CI/CD， https://DevOps.com/i-want-to-do-continuous-deployment/
[5] CI/CD全貌， https://rickhw.github.io/2019/03/28/DevOps/DevOpsTaiwan-Meetup-Beginning-in-Artifacts-Management/
[6] 軟體開發看CI/CD， https://rickhw.github.io/2017/09/14/SoftwareEngineering/Software-Development-Lifecycle/
[7] Jenkins, https://www.jenkins.io/zh/
[8] Jenkins主從架構, https://www.edureka.co/blog/jenkins-master-and-slave-architecture-a-complete-guide/
[9] Jenkins報表, http://jenkinsci.github.io/performance-plugin/Reporting.html
[10] State of DevOps 2021 - Google, https://services.google.com/fh/files/misc/state-of-DevOps-2021.pdf
[11] Google Dora Research,DORA research program (DevOps-research.com)
[12] Google Dora Quick Check, https://www.DevOps-research.com/quickcheck.html#questions
[13] 台灣DevOps能力調查, https://www.iThome.com.tw/article/152581
[14] Kim， & Gene. (2016). The DevOps Handbook.
[15] Gene kim， Kevin behr， & George spafford. (2013). The Phoenix Project: A Novel About IT， DevOps， and Helping Your Business Win. IT Revolution Press.
[16] Jez humble， & David farley. (2010). Continuous Delivery: Reliable Software Releases through Build， Test， and Deployment Automation. Addison-Wesley Professional.
[17] Nicole forsgren phd， Jez humble ， & gene kim . (2018). Accelerate: The Science of Lean Software and DevOps. IT Revolution Press.
[18] Paul m. duvall， Steve matyas， & Andrew glover. (2007). Continuous Integration: Improving Software Quality and Reducing Risk. Addison-Wesley Professional.
[19] Rick Hwang. “Ops as Code Using Serverless.” Complete Think， 2018， https://rickhw.github.io/2017/09/14/SoftwareEngineering/Software-Development-Lifecycle/.
[20] Eric j. braude, & Michael e. bernstein. (2016). Software Engineering: Modern Approaches (2nd ed.). Software Engineering: Modern Approaches.
[21] DevOps 工具元素週期表, https://DevOps.phodal.com/home
[22] Research methods for business: a skill-building approach, & Roger bougie. (2016). Research Methods for Business: A Skill-Building Approach. John Wiley
[23] Spinnaker, https://spinnaker.io/
[24] DevOps興起, https://www.ithome.com.tw/news/96861
[25] Netflix: Continuous Delivery with Spinnaker, Global Continuous Delivery with Spinnaker | by Netflix Technology Blog | Netflix TechBlog