Continuous Delivery with Docker and Jenkins by Rafał Leszko
Polling SCM trigger is a little less intuitive. The following figure presents the communication:
Jenkins periodically calls GitHub and checks if there was any push to the repository. Then, it starts the build. It may sound counter-intuitive, however, there are at least two good cases for using this method:
- Jenkins is inside the firewalled network (which GitHub does not have access to)
- Commits are frequent and the build takes a long time, so executing a build after every commit would cause an overload
The configuration of poll SCM is also somehow simpler because the way to connect from Jenkins to GitHub is already set up (Jenkins ...
Get Continuous Delivery with Docker and Jenkins now with O’Reilly online learning.
O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.
-