Jenkins Learning Note Series 3--trigger plugin configuration

First, Jenkins built-in trigger plug-in

1) build after other projects is built

You can set up multiple dependent jobs and start this build when any of the dependent jobs succeeds. Multiple dependent jobs are used, separated.

2) Trigger builds remotely (e.g., from scripts)

Specify Token_name in authentication token, and you can then start the build by connecting Jenkins_url/job/jobname/build?token=token_name.

3) Build periodically

Set in schedule, syntax is similar to cron syntax.

Cycle for project Construction (it does not care source changes), my configuration is as follows:

0 2 * * * (the source code must be build once a day 2:00)

4) Poll SCM

Set the time interval in schedule to crawl the SCM server and, if there is a new modification, start the build. So the role here is equivalent to continous build

Check the source code changes regularly (according to the SCM software version number), if there is an update checkout the latest code down, and then perform the build action. My configuration is as follows:

*/5 * * * * (check the source changes every 5 minutes)

Second, the other trigger plug-in

You need to install the plugin manually.

Installation method: Plug-in management----Advanced---Upload the downloaded plug-in (the default upload is installed)

Maven-dependency-update-trigger: Start build when there is a new Maven dependency detected, similar to the continuous build.

Buildresult-trigger: Start this build based on the success or failure of another job.

Files-found-trigger: detects the specified directory and starts build if a file of the specified schema is found.

Jenkins Learning Note Series 3--trigger plugin configuration