Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-39143

Stage view disappears after restarting jenkins

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None

      After restarting jenkins (no jobs were running), my stage view disappeared. When I go to the ajax page, I'm getting:

      Caused by: java.lang.IllegalStateException: Could not load matching start node: java.io.IOException: java.util.concurrent.ExecutionException: java.io.FileNotFoundException: D:\build\Jenkins\jobs\MasterCI\builds\54\workflow\3.xml (The system cannot find the path specified)

      The 3.xml file is in fact missing and is referenced by other xml files in the folder.

          [JENKINS-39143] Stage view disappears after restarting jenkins

          Clint Chapman created issue -

          Tim Benke added a comment -

          I get the exact same error about a missing 3.xml with Jenkins 2.46.1 and Pipeline Stage View Plugin 2.6

          Tim Benke added a comment - I get the exact same error about a missing 3.xml with Jenkins 2.46.1 and Pipeline Stage View Plugin 2.6

          Joachim Herb added a comment -

          Joachim Herb added a comment - Possible duplicate of: https://issues.jenkins-ci.org/browse/JENKINS-40057  

          Tim Benke added a comment -

          This error seems to be a little different, because an XML file is missing while with the other bug an XML file cannot be read.

          Tim Benke added a comment - This error seems to be a little different, because an XML file is missing while with the other bug an XML file cannot be read.

          Clint Chapman added a comment -

          I think it is the same issue as 40057.  From the error posted on 40057:

          Caused by: java.lang.IllegalStateException: Could not load matching start node: java.io.IOException: java.util.concurrent.ExecutionException: java.io.IOException: failed to load flow node from D:\Jenkins\jobs\stability_post_nightly1\builds\212\workflow\4.xml: <?xml version='1.0' encoding='UTF-8'?>

          Clint Chapman added a comment - I think it is the same issue as 40057.  From the error posted on 40057: Caused by: java.lang.IllegalStateException: Could not load matching start node: java.io.IOException: java.util.concurrent.ExecutionException: java.io.IOException: failed to load flow node from D:\Jenkins\jobs\stability_post_nightly1\builds\212\workflow\4.xml: <?xml version='1.0' encoding='UTF-8'?>

          Piotr Mis added a comment -

          I am observing the same issue.

          From time to time 3.xml file (in job/<build>/workflow folder) is missing.

          When I copy this file from jobs which have it Stage View appears again.

          I have managed to check to which pipeline step this is linked - and it looks that for "node" assignment (at least in 3.log file there is following text:

          Running on master in c:\j\workspace\xxxx

           

          PS. When issue appears "Pipeline Steps" view is also not working.

          Piotr Mis added a comment - I am observing the same issue. From time to time 3.xml file (in job/<build>/workflow folder) is missing. When I copy this file from jobs which have it Stage View appears again. I have managed to check to which pipeline step this is linked - and it looks that for "node" assignment (at least in 3.log file there is following text: Running on master in c:\j\workspace\xxxx   PS. When issue appears "Pipeline Steps" view is also not working.
          Daniel Geißler made changes -
          Component/s New: pipeline-stage-view-plugin [ 21139 ]
          Daniel Geißler made changes -
          Component/s New: pipeline [ 21692 ]

          Seems to be a rather important Issue, even though the visible symptoms are not that important, but as it seems the serialization of the build results is broken (thus preventing repeatable build mechanics after restarts) - which is one of the major features of jenkins pipelines scripts right?

          How about raising the priority?

          Daniel Geißler added a comment - Seems to be a rather important Issue, even though the visible symptoms are not that important, but as it seems the serialization of the build results is broken (thus preventing repeatable build mechanics after restarts) - which is one of the major features of jenkins pipelines scripts right? How about raising the priority?

          Mor L added a comment -

          Having the same issue :

          Could not load matching start node: java.io.IOException: java.util.concurrent.ExecutionException: java.nio.file.NoSuchFileException: <path to job>\builds\5\workflow\5.xml

          Running with Jenkins 2.73.3 on Windows, Pipeline 2.5

          Mor L added a comment - Having the same issue : Could not load matching start node: java.io.IOException: java.util.concurrent.ExecutionException: java.nio.file.NoSuchFileException: <path to job>\builds\5\workflow\5.xml Running with Jenkins 2.73.3 on Windows, Pipeline 2.5

            Unassigned Unassigned
            cchapman Clint Chapman
            Votes:
            38 Vote for this issue
            Watchers:
            46 Start watching this issue

              Created:
              Updated: