Jenkins loses track on build queue when reloading configuration while a build runs

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

XMLWordPrintable

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major
    • Component/s: core
    • Environment:
      Windows XP SP3
      Jenkins ver. 1.414

      I have an annoying bug occurring each time I reload the configuration of Jenkins.
      It happens only when a job is running at the time of the configuration reload. It doesn't matter how it is achieved. As soon as the reload is taking place does the build log queue freak out.
      The log of the currently build jobs do disappear.
      If you have a tab opened to the log while reloading is there at time being no problem with that particular tab until your reload it. It will then end up with an 500 http response code.
      Occasionally does Jenkins crash when reloading and attempting to access the log file.

      Take care
      Jan Seidel

            Assignee:
            Unassigned
            Reporter:
            Jan Seidel
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: