Currently, only plugins that extends from SCM have a footprint in the
polling phase. In a job only one SCM(or none) plugin is allowed to
handle the polling, no other plugin can intervene.
I propose two new extension points, one before the actual polling and
one after the polling.
This will allow other plugins to have a footprint in the polling
phase, before and after. Just like the RunListener.
[JENKINS-14178] Add an SCM poll listener
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Workflow | Original: JNJira [ 144809 ] | New: JNJira + In-Review [ 191192 ] |