CI is intended to be used with automated tests created by test-driven development (TDD). This works if everyone pushes to the master. However, we consider heavy use of branches normal: we love feature-branches, bug-branches, throwaway branches, etc. This complicates the “continuousness” of the integration. This session is about complexity of CI in the presence of feature branches and how to handle it. We define functionality to make CI and feature branches play together well and show how to implement it in Jenkins using open source plugins.