出版

推廣主幹開發的相關書籍


Software Configuration Management Patterns (November 14, 2003)

Software Configuration Management Patterns: Effective Teamwork, Practical Integration
軟體配置管理模式:有效的團隊合作,實用的整合

by Stephen P. Berczuk with Brad Appleton
Amazon (paperback)


Continuous Integration (June 29, 2007)

Continuous Integration: Improving Software Quality and Reducing Risk
持續整合:提升軟體品質和降低風險

by Paul M. Duvall, Steve Matyas, Andrew Glover
Amazon (hardback, kindle)


Continuous Delivery (July 27, 2010)

Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation
持續交付:利用自動化的建置、測試與部署完美創造出可信賴的軟體發布

by Jez Humble and Dave Farley
Amazon (hardback, kindle)
InformIT (pdf, epub, mobi)
Translations: 中文 | 日本語 | 한국말 | português

Lean Enterprise (January 3, 2015)

Lean Enterprise: How High Performance Organizations Innovate at Scale
精實企業:高績效組織如何達成創新規模化

by Jez Humble, Joanne Molesky and Barry O'Reilly
Amazon (hardback, kindle)
O'Reilly (pdf, epub, mobi)
Translations: 中文 | 日本語 | Deutsch | português


Build Quality In (February 27, 2015)

Build Quality In: Continuous Delivery and DevOps Experience Reports
建立品質:持續交付和 DevOps 經驗報告

by Steve Smith and Matthew Skelton
Leanpub (kindle)


DevOps Handbook (October 6, 2016)

The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations
DevOps Handbook:打造世界級技術組織的實踐指南

by Gene Kim, Jez Humble, Patrick Debois, John Willis, John Allspaw
Amazon (hardback, kindle)
O'Reilly (pdf, epub, mobi)


Measuring Continuous Delivery (2017)

Measuring Continuous Delivery: The what, why, and how of measuring Continuous Delivery
評估持續交付:評估交付整合的目的、原因和方法

by Steve Smith
Leanpub (kindle)


Reports promoting Trunk-Based Development


More Engineering, Less Dogma (Oct 18, 2013)

More Engineering, Less Dogma: The Path Toward Continuous Delivery Of Business Value
更多的工程技術,少一些教條:邁向持續交付商業價值之路

by Kurt Bittner and Glenn O’Donnell
Forrester Research - link


The Role of Continuous Delivery in IT and Organisational Performance (Oct 27, 2015)

The Role of Continuous Delivery in IT and Organizational Performance
持續交付在 IT 和組織績效中的角色

by Nicole Forsgren and Jez Humble
Proceedings of the Western Decision Sciences Institute - link


2015 State of DevOps Report

A survey of thousands of software development professionals distilled into a report that determines practices for the highest achieving organizations
一份從數千名軟體開發專業人士調查中提煉出的報告,確定最高成就組織的實踐方法

It was gratifying, though unsurprising, to find that deployment pain was predicted by whether the key continuous delivery practices had been implemented: comprehensive test and deployment automation, the use of continuous integration including Trunk-Based Development, and version control of everything required to reproduce production environments
讓人欣慰但也不意外的是,我們發現部署困難與關鍵的持續交付實踐方法的實施程度有關:包括全面的測試和部署自動化、使用持續整合(包括基於主幹的開發)以及對所有需要重現正式環境的內容進行版本控制。
by Puppet Labs
Puppet's download form for the report


2016 State of DevOps Report

As their 2015 report, a survey of thousands of software development professionals distilled into a report that determines practices for the highest achieving organizations
根據他們於2015年的報告,這份調查結果彙總了數千名軟體開發專業人士的意見,並確定了最高成就組織的實踐方法。

The idea that developers should work in small batches off master [main since 2020] or trunk rather than on long-lived feature branches is still one of the most controversial ideas in the Agile canon, despite the fact it is the norm in high-performing organizations such as Google. Indeed, many practitioners express surprise that this practice is in fact implied by continuous integration, but it is: The clue is in the word 'integration.'
開發者應該以小批次的方式從主分支或主幹上進行工作,而不是在長期存在的功能分支上進行工作。儘管這在高效能組織(如Google)中是常態,但這個觀點仍然是敏捷開發中最具爭議性的想法之一。實際上,許多從業人員對這個實踐方式感到驚訝,因為它實際上是持續整合的一個隱含要求,關鍵在於「整合」這個詞。
by Puppet Labs
Puppet's download form for the report


2017 State of DevOps Report

As their 2016 report, a survey of thousands of software development professionals distilled into a report that determines practices for the highest achieving organizations
根據他們於2016年的報告,這份調查結果彙總了數千名軟體開發專業人士的意見,並確定了最高成就組織的實踐方法。

Last year, we investigated the role that trunk-based development plays in continuous delivery. While our experience shows that developers in high-performing teams work in small batches and develop off of trunk or master [main since 2020], rather than long-lived feature branches, many practitioners in the industry routinely work in branches or forks.
去年,我們調查了主幹開發在持續交付中的角色。雖然我們的經驗表明,高效能團隊的開發者通常以小批次方式從主幹或主分支進行開發,而不是使用長期存在的功能分支,但許多從業人員在業界仍習慣於使用分支或 fork 版本。
by Puppet Labs
Puppet's download form for the report