In the current chapter we will learn about pre-tested commits and the means to achieve them using Jenkins. We will do this by leveraging the Distributed nature of Git and Merge before build feature of Jenkins.
Pre-tested Commits
Continuous Integration requires developers to publish each and every change (commit) to the Integration/Master branch. All these changes (on the Integration/Master branch) are built, tested, and analyzed for quality, and only after this we know if a change is good or bad. Pre-tested commits (Gated Check-in), on the other hand, ensures that not all, but ...
