Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-16714

Plugin dynamic load doesn't init PeriodicWork and AperiodicWork extensions

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Minor Minor
    • core
    • None

      PluginManager.dynamicLoad(..) doesn't properly load/init extensions of PeriodWork and AperiodicWork. Still trying to figure out why. =)

          [JENKINS-16714] Plugin dynamic load doesn't init PeriodicWork and AperiodicWork extensions

          Andrew Bayer added a comment -

          Ok, it looks like dynamicLoad(..) never ends up calling PeriodicWork.run() - I'm not sure where that's supposed to be called normally.

          Andrew Bayer added a comment - Ok, it looks like dynamicLoad(..) never ends up calling PeriodicWork.run() - I'm not sure where that's supposed to be called normally.

          Daniel Beck added a comment -

          Regularly started during Jenkins startup by AperiodicWork.init() (etc.) because it's annotated @Initializer(after=JOB_LOADED)..

          The perfect place to do this would probably be Jenkins.refreshExtensions. In fact, it says:

          // TODO: we need some generalization here so that extension points can be notified when a refresh happens?

          Daniel Beck added a comment - Regularly started during Jenkins startup by AperiodicWork.init() (etc.) because it's annotated @Initializer(after=JOB_LOADED) .. The perfect place to do this would probably be Jenkins.refreshExtensions . In fact, it says: // TODO: we need some generalization here so that extension points can be notified when a refresh happens?

            Unassigned Unassigned
            abayer Andrew Bayer
            Votes:
            2 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: