Status: Closed (View Workflow)
Environment:O.S.: Ubuntu 15.04 (Vivid)
Jenkins Version: 2.32.1 LTS
JDK version: OpenJDK Runtime Environment (build 1.8.0_45-internal-b14)
Setting the "Build Periodically" setting for a multibranch pipeline job implies that the job will be run at that interval. But the setting is intended to trigger periodic rescans of the repo, not periodic builds.
The inline documentation implies that the build will be run periodically, as opposed to the branch indexing. This is misleading:
Provides a cron-like feature to periodically execute this project.
This feature is primarily for using Jenkins as a cron replacement, and it is not ideal for continuously building software projects. When people first start continuous integration, they are often so used to the idea of regularly scheduled builds like nightly/weekly that they use this feature. However, the point of continuous integration is to start a build as soon as a change is made, to provide a quick feedback to the change. To do that you need to hook up SCM change notification to Jenkins.
So, before using this feature, stop and ask yourself if this is really what you want.
|Field||Original Value||New Value|
|Labels||scm-api-tidy-scrub ux||scm-api-tidy ux|
|Component/s||cloudbees-folder-plugin [ 18137 ]|
|Component/s||branch-api-plugin [ 18621 ]|
|Assignee||Stephen Connolly [ stephenconnolly ]||CloudBees Inc. [ cloudbees ]|
|Assignee||CloudBees Inc. [ cloudbees ]||Stephen Connolly [ stephenconnolly ]|
|Status||Open [ 1 ]||In Progress [ 3 ]|
|Remote Link||This issue links to "PR#89 (Web Link)" [ 15512 ]|
|Remote Link||This issue links to "branch-api#90 (Web Link)" [ 15513 ]|
|Status||In Progress [ 3 ]||Resolved [ 5 ]|
|Resolution||Fixed [ 1 ]|
|Status||Resolved [ 5 ]||Closed [ 6 ]|
|Remote Link||This issue links to "CloudBees Internal OSS-2063 (Web Link)" [ 18437 ]|