Jenkins cron format

In Jenkins, our SCM polling schedule is set to * * * * * . But Jenkins suggests Do you really mean "every minute" when you say "* * * * *"? Perhaps you meant "0 * * * *" Do you really mean "every minute" when you say "* * * * *"? Perhaps you meant "0 * * * *"

Is there a difference between * * * * * and 0 * * * * ?

+7
source share
3 answers

Of course there is a difference!

0 * * * * - every hour when the minute == 0. (i.e. 1:00, 2:00, ..)

* * * * * - every minute

More about guide .

+13
source

Every fifteen minutes (possibly from: 07 ,: 22 ,: 37 ,: 52)

 H/15 * * * * 

Every ten minutes in the first half of every hour (three times, possibly by: 04::14 a.m:24)

 H(0-29)/10 * * * * 

Once every two hours at 45 minutes after the hour starting at 9:45 and ending at 15:45 every weekday.

 45 9-16/2 * * 1-5 

Once every two hours between 9:00 and 17:00 every weekday (maybe at 10:38, 12:38, 14:38, 16:38)

 HH(9-16)/2 * * 1-5 

Once a day on the 1st and 15th day of each month, except December

 HH 1,15 1-11 * 
+7
source

The SCM poll will ping the source code that is configured in the Jenkins project, and if there are any new commits from the previous assembly, then only it will invoke the assembly. If you want to call the assembly by overriding this, use the Build Periodically function

+1
source

All Articles