on failure with a configuration reload, jenkins log error but don't warn user for inconsistent state

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

XMLWordPrintable

      During a configuration reload, config_reloader worker has been interrupted.
      The result is that a set of job disappeared from jenkins, and an error has been logged, but the general Jenkins state didn't change to reflect this broken state.

      Shouldn't Jenkins switch to safe-restart mode on such an error, or at least warn user with a top banner message that some data have been corrupted and a restart is recommended ?

            Assignee:
            Unassigned
            Reporter:
            Nicolas De Loof
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: