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

Plugin dynamic load doesn't init PeriodicWork and AperiodicWork extensions

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Minor
    • Resolution: Duplicate
    • core
    • None

    Description

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

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-28683 PeriodicWork.init() / AperiodicWork.init() does not work for dynamically-loaded plugins

          • Major - Major loss of function.
          • Closed
          is blocking

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-23377 cron driven backups never happen

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            abayer 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.

            abayer 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.
            danielbeck 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?

            danielbeck 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?

            People

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

              Dates

                Created:
                Updated:
                Resolved: