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

Build flow graphs are missing on all run pages after Jenkins is restarted

    Details

    • Similar Issues:

      Description

      After Jenkins is restarted, build flow graphs disappear from all job run pages.

        Attachments

          Activity

          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Nicolas De loof
          Path:
          src/main/groovy/com/cloudbees/plugins/flow/JobInvocation.groovy
          src/main/java/com/cloudbees/plugins/flow/FlowRun.java
          http://jenkins-ci.org/commit/build-flow-plugin/b9628afa8ff725cf2933e649b1a09995953bb764
          Log:
          Merge pull request #28 from masterhard/jenkins-18003

          [FIXED JENKINS-18003]

          Compare: https://github.com/jenkinsci/build-flow-plugin/compare/277fb8f392d0...b9628afa8ff7

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Nicolas De loof Path: src/main/groovy/com/cloudbees/plugins/flow/JobInvocation.groovy src/main/java/com/cloudbees/plugins/flow/FlowRun.java http://jenkins-ci.org/commit/build-flow-plugin/b9628afa8ff725cf2933e649b1a09995953bb764 Log: Merge pull request #28 from masterhard/jenkins-18003 [FIXED JENKINS-18003] Compare: https://github.com/jenkinsci/build-flow-plugin/compare/277fb8f392d0...b9628afa8ff7
          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Dmitry Korotkov
          Path:
          src/main/groovy/com/cloudbees/plugins/flow/JobInvocation.groovy
          src/main/java/com/cloudbees/plugins/flow/FlowRun.java
          http://jenkins-ci.org/commit/build-flow-plugin/6e09ecce3ee4ddef6fd287d8c34708d2ce41cab2
          Log:
          [FIXED JENKINS-18003]

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Dmitry Korotkov Path: src/main/groovy/com/cloudbees/plugins/flow/JobInvocation.groovy src/main/java/com/cloudbees/plugins/flow/FlowRun.java http://jenkins-ci.org/commit/build-flow-plugin/6e09ecce3ee4ddef6fd287d8c34708d2ce41cab2 Log: [FIXED JENKINS-18003]
          Hide
          masterhard Dmitry Korotkov added a comment -

          I looked into the sources and it turned out that build graph is persisted in build.xml, but when it is loaded, it is overwritten by field initializer in FlowRun.java.

          Also, in JobInvocation.groovy some build fields are returned without using getBuild() method, so lazy wiring JobInvocation object with actual Build object is skipped causing all builds displayed as not started on a graph loaded from disk.

          Sending a pull request for this fix.

          Show
          masterhard Dmitry Korotkov added a comment - I looked into the sources and it turned out that build graph is persisted in build.xml, but when it is loaded, it is overwritten by field initializer in FlowRun.java. Also, in JobInvocation.groovy some build fields are returned without using getBuild() method, so lazy wiring JobInvocation object with actual Build object is skipped causing all builds displayed as not started on a graph loaded from disk. Sending a pull request for this fix.

            People

            • Assignee:
              ndeloof Nicolas De Loof
              Reporter:
              masterhard Dmitry Korotkov
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: