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

Mandate consistent iteration order for DepthFirstScanner

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • workflow-api-plugin
    • None

      DepthFirstScanner in the graphanalysis APIs works, but the API mandates that it visit the first node then the branches after (but in reverse order).

      Instead we should visit the branches in order for drop-in compatibility with FlowGraphWalker

      This will, incidentally, fix JENKINS-38457.

          [JENKINS-38458] Mandate consistent iteration order for DepthFirstScanner

          Sam Van Oort created issue -
          Sam Van Oort made changes -
          Assignee New: Sam Van Oort [ svanoort ]
          Jesse Glick made changes -
          Description Original: DepthFirstScanner in the graphanalysis APIs works, but the API mandates that it visit the *first* node then the branches after (but in reverse order).

          Instead we should visit the last first, then then others, as with ForkScanner in [JENKINS-38309|https://issues.jenkins-ci.org/browse/JENKINS-38309].

          This will, incidentally, fix https://issues.jenkins-ci.org/browse/JENKINS-38381 too.
          New: DepthFirstScanner in the graphanalysis APIs works, but the API mandates that it visit the *first* node then the branches after (but in reverse order).

          Instead we should visit the last first, then then others, as with ForkScanner in JENKINS-38309.

          This will, incidentally, fix JENKINS-38381 too.

          Jesse Glick added a comment -

          JENKINS-38457 did you mean?

          Jesse Glick added a comment - JENKINS-38457 did you mean?

          Jesse Glick added a comment -

          Does not fix JENKINS-38457, since that requires FlowGraphTable to also reverse its parallel branches.

          Jesse Glick added a comment - Does not fix JENKINS-38457 , since that requires FlowGraphTable to also reverse its parallel branches.
          Jesse Glick made changes -
          Link New: This issue relates to JENKINS-38457 [ JENKINS-38457 ]

          Code changed in jenkins
          User: Sam Van Oort
          Path:
          src/main/java/org/jenkinsci/plugins/workflow/graphanalysis/DepthFirstScanner.java
          http://jenkins-ci.org/commit/workflow-api-plugin/3baae43984b507100343473c61c6c7615085d02e
          Log:
          Make DepthFirstScanner obey last->first parallel branch ordering per JENKINS-38458

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Sam Van Oort Path: src/main/java/org/jenkinsci/plugins/workflow/graphanalysis/DepthFirstScanner.java http://jenkins-ci.org/commit/workflow-api-plugin/3baae43984b507100343473c61c6c7615085d02e Log: Make DepthFirstScanner obey last->first parallel branch ordering per JENKINS-38458
          Sam Van Oort made changes -
          Description Original: DepthFirstScanner in the graphanalysis APIs works, but the API mandates that it visit the *first* node then the branches after (but in reverse order).

          Instead we should visit the last first, then then others, as with ForkScanner in JENKINS-38309.

          This will, incidentally, fix JENKINS-38381 too.
          New: DepthFirstScanner in the graphanalysis APIs works, but the API mandates that it visit the *first* node then the branches after (but in reverse order).

          Instead we should visit the branches in order for drop-in compatibility with FlowGraphWalker

          This will, incidentally, fix JENKINS-38381.
          Sam Van Oort made changes -
          Description Original: DepthFirstScanner in the graphanalysis APIs works, but the API mandates that it visit the *first* node then the branches after (but in reverse order).

          Instead we should visit the branches in order for drop-in compatibility with FlowGraphWalker

          This will, incidentally, fix JENKINS-38381.
          New: DepthFirstScanner in the graphanalysis APIs works, but the API mandates that it visit the *first* node then the branches after (but in reverse order).

          Instead we should visit the branches in order for drop-in compatibility with FlowGraphWalker

          This will, incidentally, fix JENKINS-38457.
          Sam Van Oort made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]

            svanoort Sam Van Oort
            svanoort Sam Van Oort
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: