Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-9605

Task last run and last result not persisted correctly

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 3.0.0-m7, 3.6.0
    • Fix Version/s: 3.13.0
    • Component/s: Database, Scheduled Tasks, UX
    • Labels:
    • Environment:
      Chrome MacOSX
    • Story Points:
      2

      Description

      The last run time of scheduled tasks is not persisted correctly. The symptom is that a task runs(starts) on a regular schedule ( ie. weekly) and may have a last run time that is much farther in the past than the actual last start of the task.

      Expected

      When a task is started and then running while Nexus is stopped, then on restart

      • last run time¬†shows when that task was last started
      • last result duration will be time of server shutdown ( or very close to it) minus last start time
      • last result will NOT be "Ok" since the task was abruptly stopped while running by server shutdown. Error may not be good enough either. Need a state that suggests task was forcibly stopped, not by a request from the UI or REST call, but server shutdown, clean or otherwise.

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            jtom Joe Tom
            Last Updated By:
            Peter Lynch
            Team:
            Nexus - Platform
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Date of First Response:

                tigCommentSecurity.panel-title