Whenever we push code changes to Git, we want our Jenkins project to start as soon as possible. After all, the sooner we know something is broke, the easier it is for us to fix it. You have probably already seen the Build Triggers section in the configuration of your Jenkins project. There are four build triggers currently available to us.
First, we can build the project remotely, which we will not do. Second, we can build after other projects, which is handy when you have multiple projects that depend on each other. Next is the periodic build, which should speak for itself. And last, we have the poll SCM option, which polls your SCM-in our case Git-for changes and triggers a build when something changed.
For now, we will look at the periodic build and the poll SCM triggers. Both use cron syntax (cron comes from the Greek word for time, chronos), which I find rather...
