-
Bug
-
Resolution: Fixed
-
Major
PeriodicWork.init() / AperiodicWork.init() are run after JOB_LOADED. If a plugin is subsequently installed which includes such an extension, its work is not run until after a Jenkins restart.
Should use the new ExtensionListListener to detect this case and start the task.
- is duplicated by
-
JENKINS-16714 Plugin dynamic load doesn't init PeriodicWork and AperiodicWork extensions
-
- Resolved
-
- links to
[JENKINS-28683] PeriodicWork.init() / AperiodicWork.init() does not work for dynamically-loaded plugins
Workflow | Original: JNJira [ 163537 ] | New: JNJira + In-Review [ 181275 ] |
Summary | Original: PeriodicWork.init() does not work for dynamically-loaded plugins | New: PeriodicWork.init() / AperiodicWork.init() does not work for dynamically-loaded plugins |
Description |
Original:
{{PeriodicWork.init()}} is run after {{JOB_LOADED}}. If a plugin is subsequently installed which includes such an extension, its work is not run until after a Jenkins restart. Should use the new {{ExtensionListListener}} to detect this case and start the task. |
New:
{{PeriodicWork.init()}} / {{AperiodicWork.init()}} are run after {{JOB_LOADED}}. If a plugin is subsequently installed which includes such an extension, its work is not run until after a Jenkins restart. Should use the new {{ExtensionListListener}} to detect this case and start the task. |
Assignee | New: James Nord [ teilo ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Status | Original: In Progress [ 3 ] | New: In Review [ 10005 ] |
Remote Link | New: This issue links to "PR 3496 (Web Link)" [ 20841 ] |
Link |
New:
This issue is duplicated by |
Labels | New: lts-candidate |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Review [ 10005 ] | New: Closed [ 6 ] |