I mentioned in my last post how we have started using Feature Branches with Git and Jenkins. In that, I rather casually mentioned that
“The build server uses the Git plugin for Jenkins to monitor all the branches on the local repository. Whenever a developer pushes to the repository, Jenkins will see the change and try to merge it into the stable branch. If the build passes, the merge is committed. If it doesn’t pass, the FeatureBranch doesn’t get merged – and it will stay unmerged until another change is made against it.”
This feature means that broken builds have almost no impact on team productivity. In fact – it can even be more productive to allow a broken build than to try to prevent it all the time.
Continue reading “Git, Feature Branches, and Jenkins – or how I learned to stop worrying about broken builds”