擺線

2023年6月21日

DevOps.com擺線添加模板簡化GitOps工作流6月21日,2023年擺線今天增加了一個引導堆棧功能提供DevOps團隊有能力構建Git模板或使用的由公司定義雲計算環境。能力是通過門戶訪問添加到擺線自動化軟件交付平台。這也使簡單的DevOps團隊重用模板起程拓殖或Kubernetes環境兼容。在未來幾個月,擺線計劃釋放頭,一個元數據工具,自動填充項目參數顯示頁麵和項目管理工具為每個開發環境提供一個統一的視圖,包括持續集成/持續交付(CI / CD)管道、文檔、自動化、日誌、雲成本和碳排放。擺線創始人本傑明Brial說模板提供了一個抽象層,使它容易實現GitOps工作流。作為一項最佳實踐,GitOps使DevOps團隊統一管理代碼提供IT基礎設施和軟件交付。然而,僅提供一個Git倉庫不足,Brial說。DevOps團隊需要訪問一組模板,自動化過程和消除否則一組複雜的任務是什麼,他說。還很容易發現模板消除組織的傾向於創建冗餘自動化僅僅因為一個開發團隊無法找到現有的框架,另一個團隊已經創建,Brial補充道。這種方法還允許DevOps團隊更容易接受平台工程原則集中DevOps使用引導服務目錄管理嵌入到擺線平台,Brial說。 That capability makes it possible to enforce GitOps policies in a way the developers will have to respect because the automation frameworks are readily available, he added. It’s not clear whether organizations are embracing platform engineering. Historically, adoption of DevOps workflows in most organizations has tended to flow from the bottom up. As a result, it’s fairly common for multiple application development teams within an organization to have adopted multiple DevOps platforms to manage workflows. Advocates for platform engineering are making a case for eliminating many of those redundant platforms in favor of a corporate standard. At the core of any approach is the assumption that centralization will reduce costs by eliminating redundancy. Issues can arise, however, when centralization results in loss of flexibility. Many of the teams that adopt DevOps want to be able to add and replace tools as they see fit. If there is a corporate standard that narrows their tool options, it’s just a matter of time before those teams start to look for ways around the corporate standard. Each organization will need to strike a balance between flexibility and the need to bring some order to DevOps workflows. In the meantime, however, the pace at which multiple software development initiatives are being launched is likely to force a platform engineering conversation that, in many cases, many organizations have postponed longer than anyone cares to admit. Recent Posts By Mike Vizard