{"title":"杀死守门人:引入持续集成系统","authors":"Francis J. Lacoste","doi":"10.1109/AGILE.2009.35","DOIUrl":null,"url":null,"abstract":"This is the story of how the Launchpad (https://launchpad.net) development team switched to a continuous integration system to increase several flows in their development process: flow of changes on trunk; flow of changes requiring database schema upgrade; flow of deployed changes to end users. The switch to a buildbot-based system meant violating a very old company taboo: a trunk that doesn’t pass its test suite. The risk of a broken trunk was offset by allowing each developer to run the full test suite in the Amazon EC2 cloud.","PeriodicalId":280848,"journal":{"name":"2009 Agile Conference","volume":"27 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2009-08-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"36","resultStr":"{\"title\":\"Killing the Gatekeeper: Introducing a Continuous Integration System\",\"authors\":\"Francis J. Lacoste\",\"doi\":\"10.1109/AGILE.2009.35\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"This is the story of how the Launchpad (https://launchpad.net) development team switched to a continuous integration system to increase several flows in their development process: flow of changes on trunk; flow of changes requiring database schema upgrade; flow of deployed changes to end users. The switch to a buildbot-based system meant violating a very old company taboo: a trunk that doesn’t pass its test suite. The risk of a broken trunk was offset by allowing each developer to run the full test suite in the Amazon EC2 cloud.\",\"PeriodicalId\":280848,\"journal\":{\"name\":\"2009 Agile Conference\",\"volume\":\"27 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2009-08-24\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"36\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"2009 Agile Conference\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/AGILE.2009.35\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"2009 Agile Conference","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/AGILE.2009.35","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Killing the Gatekeeper: Introducing a Continuous Integration System
This is the story of how the Launchpad (https://launchpad.net) development team switched to a continuous integration system to increase several flows in their development process: flow of changes on trunk; flow of changes requiring database schema upgrade; flow of deployed changes to end users. The switch to a buildbot-based system meant violating a very old company taboo: a trunk that doesn’t pass its test suite. The risk of a broken trunk was offset by allowing each developer to run the full test suite in the Amazon EC2 cloud.
京公网安备 11010802042870号
京ICP备2023020795号-1
分享
求助内容：
应助结果提醒方式：
扫码关注我们
