Since state is not persistent, this attempt to handle resumed builds is unlikely to work: there will be a new UUID registered, and any service posting back to a URL obtained prior to the restart will just fail.

      There are no functional tests, much less anything using RestartableJenkinsRule, which would be the natural way to reproduce this sort of issue.


      BTW there are also open issues in GitHub which is confusing. One or the other source of issues should be disabled.

          [JENKINS-53321] Test functioning across restarts

          Jesse Glick created issue -
          Jesse Glick made changes -
          Link New: This issue relates to JENKINS-27127 [ JENKINS-27127 ]
          Jesse Glick made changes -
          Summary Original: Will not work across restarts New: Test functioning across restarts
          Alex Earl made changes -
          Assignee Original: Chris Pitman [ cpitman ] New: Alex Earl [ slide_o_mix ]
          Alex Earl made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Alex Earl made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Fixed but Unreleased [ 10203 ]

            slide_o_mix Alex Earl
            jglick Jesse Glick
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: