How does jenkins deal with builds?

[Sébastien Hinderer]

Dear all,

Currently our builds are triggered by polling the SCM system for changes
and we do the polling every 15 minutes.

As I understandi it, this means that if, say, 1 commit is pushed every
minute between two checks, only two builds will be done, one before and
one after these 15 commits.

Now I am wondering what would happen if we switch to a hook-based
trigger. Then Jenkins would be notified of each commit while the
previous build may not have been completed yet. Would that mean that
every notification would put a build in Jenkin's build queue?

Any response appreeciated, including pointers to relevant documentation.

Best wishes,

Sébastien.

[Denis]

By default Jenkins would trigger a build for each push.
You can mitigate this either by ignoring commits which have a certain message in them or throttle builds essentially making each build wait for the previous to complete before

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.