This issue is archived. You can view it, but you can't modify it. Learn more

ExportXMLWordPrintable

      It appears based on source code reading from Jenkins master branch revision 8ef4df922e47e1e002271562c2c458e764c36b89 that TimerTrigger inherits the buildRequiresWorkspace directly from SCM which return true. This makes it a synchronous trigger. I don't see why each TimerTrigger needs a workspace, it just looks like a way to put a build into the queue. As is, TimerTrigger needs to wait for a thread to become available until it can trigger a job which can at worst just mean that timer events will not be executed if other synchronous events are hogging the executor pool.

            Assignee:
            Unassigned
            Reporter:
            Seppo Yli-Olli
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: