Jenkins timing of polling SCM Construction

A difference

Timing Construction:

Whether on a remote code branches (Svn / Git) code for updates, regular build tasks are executed

Poll SCM:

On the remote code branches (Svn / Git) as long as there are any updates, execute build tasks.

Second, the five-star format: * * * * *

  • * Indicates a first-minute minute: the value of 0-59, the first few minutes to perform
  • Second teeth * indicates hour hour: the value of 0-23, the first hours of execution
  • * Third satellite is the day day: the value of 1-31, the first few days of execution
  • * Fourth pieces represent months month: the value of 1-12, and the implementation of the first few months
  • The fifth day of the week * stars week: the value of 0-7, the first implementation of a few days a week.

Third, examples

# Every half hour to be built once every half hour OR a remote check code branches, the update Construction
H/30 * * * *

# Every two hours OR once every two hours to build a remote check code branches, the update Construction
H H/2 * * *

# Day two in the morning timed to build
H 2 * * *

# Month on the 15th execution building
H H 15 * *

# Weekdays, 9 am sharp execution
H 9 * * 1-5

# Week 1,3,5, from 8:30, 19:30 off, 30 minutes every 4 hours to build a 
H / 30 8-20 / 4 * * 1,3,5

IV Summary

During polling or constructed using the timing SCM need to see specific scenario, the following two common scenarios listed for reference.

# Daily 8:00 construct the timing, regardless of whether the code updates
H 8 * * *

# Days, a daily timing of 8:00 constructed, every 30 minutes during 9-20 inspection time point, there is constructed a code update 
timing of Construction: H 8 * * * 
polling the SCM: H / 30 * * 1-5 9-20

After configuration, you can click on the application, check the configuration (Configuration will prompt illegal) or to https://crontab.guru test verification.

Guess you like

Origin www.cnblogs.com/panda-sweets/p/12554200.html