https://citconf.com/wiki/index.php?action=history&feed=atom&title=How_to_spread_CI_to_the_team 2026-04-24T23:23:42Z Revision history for this page on the wiki MediaWiki 1.35.11 https://citconf.com/wiki/index.php?title=How_to_spread_CI_to_the_team&diff=15517&oldid=prev 2013-10-01T17:13:46Z

<p>Spreading CI to the team</p> <p><b>New page</b></p><div>== How to spread CI to the team: ==<br /> <br /> ==== Why bother? ====<br /> * Spread the burden of maintaining the system<br /> * The more that people ensure their code/new feature is easily testable the greater the reduction in complexity of the CI system making it more reliable<br /> * Consequences of bad builds are potentially costly<br /> <br /> ==== War Story: ====<br /> * Fed up doing &quot;continuous repairing&quot; of the build where one person was maintaining the build and tracking down issues when a break was encountered<br /> * Very time consuming and difficult because people were still submitting changes after the build was broken potentially adding other issues<br /> * Made producing builds for demos potentially a nightmare<br /> <br /> ==== How do we change the culture to ensure that developers make their code easily testable and or add tests? ====<br /> * Educate the developers on how to use the testing framework<br /> * Remove any barriers for running the tests (i.e. keep the process as simple as possible)<br /> <br /> ==== Alternative to requiring a change in culture: ====<br /> * Separate features are developed on a separate branch that is automatically spun up from mainline<br /> * Feature branch must run through all tests up to the acceptance tests before being allowed to submit back to mainline<br /> <br /> ==== Example setups: ====<br /> * Jira - Team City - Git<br /> * Subversion for mainline - Git for branches<br /> * Team Foundation Server for mainline - Git for clients<br /> * Team City - Perforce</div>

Rua