DevOps is the combination of cultural philosophies, technical practices, and tools that fosters integration, collaboration, communication, and automation between technology operations and software development teams in order to improve the quality and speed of software delivery. The common goal of DevOps is to remove friction, risk, and other constraints to enable faster, more successful application production rollouts, as often and as rapidly as the business requires. Most companies that implement DevOps methods today still have a development team and an operations team in place. You can think of DevOps as the processes and individuals that build the bridges between these teams to improve the business and enhance the end-customer experience. Various tools and platforms facilitate the work of DevOps, but they do not define it.

How did DevOps originate?

DevOps was birthed by the practice and propagation of agile software development. Since the agile methodology speeds up the development process and throughput velocity, there was a need to alter the structure of project teams to accommodate this new reality. As agile culture took root, it became clear that having the software development and IT operations teams working separately was counterproductive and inefficient. DevOps practices automate deployment pipelines and produces faster feedback to improve efficiency, predictability, maintainability, and security. It brings developers into the production environment, gives them deeper insights into the infrastructure and gets them more involved in application lifecycle management.

Like all work cultures, DevOps is adopted and applied in different ways from organization to organization. Nevertheless, certain capabilities are common in nearly all DevOps implementations. What are DevOps key characteristics? Collaboration Instead of operations and development teams assuming a defensive or combative stance when engaging one another, they strive to collaborate. The conflicts and rivalry between these teams are one of the principal catalysts for the creation of DevOps. Automation DevOps is geared toward facilitating the speedy delivery of an agile development project. Therefore, it is heavily dependent on automation. That means a reliance on multiple tools that automate the application development and deployment cycle. Continuous Integration Continuous integration is a technique for continually merging software code from all developers in a project into a shared mainline. This ensures that the copy of the project each developer is working on is nearly the same. By compelling developers to integrate their work into the mainline at least daily, DevOps culture reduces the likelihood of disruptive merger conflicts later on. Continuous Testing Software failure is expensive. Unleashing an application release that ruins existing user experience or introduces new risks would be counterproductive. Continuous testing ensures the right balance of software quality and speedy deployment is achieved. In DevOps, software testing isn’t something left to one person or department. Rather, it’s everyone’s responsibility. Developers engineer quality into the code and then avail test data. Quality assurance and operations teams, in turn, configure test cases and the test environment. Since tests must be executed quickly to avoid falling behind new changes being applied in development, the test process must be automated as much as possible. Continuous Delivery Continuous delivery means changes to application code are automatically prepared for release into the live environment. All code changes are deployed into a test environment before they are eventually applied to production. The DevOps team always has a deployment-ready release that has successfully been taken through the standardized and automated test process. Release frequency will vary depending on goals, priority, and urgency. It may be as often as multiple releases per day or as seldom as one release per month or quarter. Continuous Monitoring Given the speed and number of releases, it’s imperative to have a solution in place that provides continuous monitoring to enable faster and better response to changing customer needs. Continuous monitoring allows the DevOps team to track software performance and improve its stability. Problems are identified quickly, and root causes proactively investigated to prevent outages and downtime. Monitoring starts during release development. The same monitoring tools that are applied in the live environment can be leveraged in development to pick up problems before they make their way into production.

Organizations that embrace DevOps might have all IT resources within a traditional data center, all resources in an offsite cloud, or distribute their resources in a hybrid environment. The DevOps movement is not defined, nor led, by traditional IT software, hardware, or management vendors. In addition, there are currently no codified rules or manuals for DevOps, only generally accepted guidelines. With that said, adoption and implementation of DevOps vary greatly from one organization to the next. The learnings of DevOps are primarily evangelized by a passionate grassroots community of IT practitioners, spread across a wide variety of IT disciplines. Most members of the DevOps community have active jobs within various organizations, and they share their learnings in numerous online and in-person forums and gatherings. Depending on the number and maturity of the practitioners in an organization, the benefits of a DevOps implementation can be significant, including: Faster release of apps with automation of integrated build, test and deployment process Increased developer and operational efficiency by managing your infrastructure as code Improved customer experience with immediate feedback loops and continuous improvement

How to Scale DevOps practices across all your environments?

Micro Focus enables you to scale DevOps practices across Hybrid IT , automating and orchestrating continuous delivery pipelines from mainframe to mobile, and providing actionable insight to securely deliver high quality software and services faster. Micro Focus helps its customers scale DevOps practices across traditional and hybrid IT environments. Enterprise DevOps can deliver in-novation by transforming and extending your current IT environments, with quality and security built in, every step of the way. The Micro Focus approach starts with under-standing where you are on your Enterprise DevOps journey. We then provide guidance on scaling your DevOps practices and help you integrate your toolchain from mainframe to mobile. We believe it’s imperative to think big and start small. Look at the system holistically, understand where the constraints are and re-move them one-by-one. We are the only vendor to provide an integrated, end-to-end application lifecycle management solution that is built for any methodology, technology, and delivery model.

什麼是 DevOps？ | Micro Focus

‹ Back

應用程式交付管理
‹ Back

應用程式交付管理
加快速度、消除瓶頸，不斷提升軟體交付能力
應用程式現代化與連線
‹ Back

應用程式現代化與連線
實現核心業務系統的現代化以推動業務轉型
安全性
‹ Back

安全性
為您所有工作的核心提供安全防護，包含營運、應用程式、身分識別與資料
資訊管理與治理
‹ Back

資訊管理與治理
值得信賴、經過法律驗證、遵循法規和隱私的解決方案
IT 作業管理
‹ Back

IT 作業管理
使 IT Operations 與 DevOps 齊頭並進
Analytics & Big Data

DevOps 是文化理念、技術實踐和工具的組合，可促進技術營運和軟體開發團隊之間的整合、協調、溝通和自動化，進而提升軟體交付的品質和速度。

DevOps 的共同目標是消除摩擦、風險和其他限制，以依據業務需求的頻率和速度更快，更成功地推出應用程式產品。

今日多數採行 DevOps 方法的公司仍擁有一個開發團隊和一個營運團隊。您可以將 DevOps 視為在這些團隊之間搭建橋樑，以改善業務並提高終端客戶體驗的流程和個體。其中的各種工具和平台可促進 DevOps 的工作，但不會對其進行定義。

DevOps 的源起為何？ DevOps 的需求解釋

DevOps誕生於敏捷軟體開發的實踐和傳播。由於敏捷方法加快了開發過程和輸送速度，因此有必要變更專案團隊的結構來適應這個新實境。顯然，隨著敏捷文化紮根，讓軟體開發團隊和 IT 營運團隊分開工作會適得其反，使效率降低。

DevOps 實踐使部署管線自動化並更快產生回饋，以提高效率、可預測性、可維護性和安全性。它使開發人員進入生產環境，使他們對基礎結構有更深入的了解，並使他們參與更多應用程式生命週期管理。

DevOps 可以為您做什麼？

像所有工作文化一樣，DevOps 的採用和應用方式因組織而異。但是，某些功能在幾乎所有 DevOps 實作中都是通用的。 DevOps 關鍵特性為何？

協同作業

當營運團隊和開發團隊彼此參與時，以協同作業替代攻擊或防禦的姿態。這些團隊之間的衝突和競爭是建立 DevOps 的主要催化劑之一。

自動化

DevOps 致力於促進敏捷開發專案的快速交付。因此，它非常倚重自動化。這意味著要依靠多種工具來完成應用程式開發和部署週期自動化。

持續性整合

持續整合是一種用於將專案中所有開發人員的軟體代碼不斷合併到共享主線（shared mainline）中的技術。這樣可以確保每個開發人員正在從事的專案的副本幾乎相同。透過迫使開發人員至少每天將其工作整合到主線中，DevOps 文化降低了未來破壞性合併衝突的可能性。

持續測試

軟體故障代價昂貴。發行會破壞目前使用者的體驗，或引入新風險的應用程式會適得其反。連續測試可確保軟體品質和快速部署之間維持適當的平衡。

在 DevOps 中，軟體測試不是一個人或一個部門要做的事情。而是每個人的責任。開發人員將品質工程師編碼到代碼中，然後利用測試資料。然後，品質保證和操作團隊將設定測試案例和測試環境。

由於必須快速執行測試以避免較開發中應用的更新落後，因此測試過程必須盡可能自動化。

持續交付

持續交付意味著應用程式代碼的變更將自動準備好發佈到即時環境中。在最終將其應用到產品之前，所有代碼變更均已部署到測試環境中。

DevOps 團隊始終具備已成功通過標準化和自動化測試流程的可部署版本。發行頻率取決於目標、優先順序和緊急程度。它可以是一天發行多次，也可以是每月或每一季發行一次。

持續監控

考慮發行的速度和數量，需要執行一個提供持續監控的解決方案，以應對不斷變化的客戶需求，快速做出優質回應。

持續監控使 DevOps 團隊能夠追蹤軟體性能，並改善其穩定性。快速識別問題，積極調查根本原因，防止設備中斷和停機。

在版本開發期間開始監控。可以在開發環節利用實際環境中使用的同款監視工具，以便在版本進入生產環境前發現問題。

為何選擇 DevOps？

擁護 DevOps 的組織可能擁有傳統資料中心內的所有 IT 資源、異地雲端中的所有資源，或在混合環境中分配其資源。

DevOps 活動並非由傳統的 IT 軟體、硬體或管理供應商定義或指導。此外，目前尚無關於 DevOps 編纂的規則或手冊，只有公認的指南。雖然如此，DevOps 的採用和實施在不同組織之間的差異很大。

DevOps 的學習主要是由熱情的 IT 從業人員基層社群傳播，這些社群涵蓋各種 IT 學科。 DevOps 社群多數成員在各組織中都有正職，他們在眾多線上和面對面的論壇和聚會中分享他們的經驗。依組織中從業人員的人數和成熟度，DevOps 實施的好處可能產生重要影響，包括：

以自動執行整合建立、測試和部署流程更快速發佈應用程式
以代碼形式管理基礎設施來提高開發人員和營運的效率
以即時回饋循環和持續改進來改善客戶體驗

跨所有環境擴展 DevOps 執行

Micro Focus 使您能夠跨混合 IT 環境擴展 DevOps 執行，自動化和協調從大型主機到移動設備的持續交付管道，並提供可行見解，以便快速安全地交付高品質的軟體和服務。

Micro Focus 幫助其客戶跨傳統和混合 IT 環境擴展 DevOps 執行。 Enterprise DevOps 可過當前 IT 環境的轉型和擴展實現創新，同時保證各個環節的品質和安全。

Micro Focus 方法首先要瞭解您在 Enterprise DevOps 旅程所處的位置。然後，我們會指導您擴展 DevOps 執行，並幫助您將工具鏈從大型主機整合到行動裝置。我們堅信大處著眼，小處著手。整體地看系統，瞭解其限制，然後逐一消除。我們是唯一能夠提供整合式端到端應用程式生命週期管理解決方案的供應商，我們的解決方案適用於任何方法、技術和交付模型。

Your browser is not supported