When running a flow of flows, the visualization only shows the graphs of the first flow of the build and in order to open the other flows, user needs to open the console output of the master job and open the link to the other flows and then open the build-graph.

      Prior to this split of plugins build-flow would show the graphs by default and would support the ability to see graphs of a flow of flows and navigate between them.

          [JENKINS-19616] Graphs dont show 2nd level flows

          robsweet added a comment -

          I'm seeing the same thing. More information:

          I have a build flow for a Pipeline and the way things are working right now, Images Pipeline wraps two parallel regular jobs, the Images-AminateAllRoles flow, and the Images-IntegrationPipeline flow. The build graph shows the first two parallel jobs, Images-AminateAllRoles and it's child jobs, and then stops.

          As you can see from the console output, it does run the second buildflow job.

          Job Output
          Building Images pipeline with Git revision b778caff96c672f2ab7a03615b68ab429a7fa279 of master
          parallel {
              Schedule job Imageserver_Tests
              Schedule job Images_API-Tests
              Build Images_API-Tests #369 started
              Build Imageserver_Tests #154 started
              Imageserver_Tests #154 completed 
              Images_API-Tests #369 completed 
          }
          Schedule job Images-AminateAllRoles
          Build Images-AminateAllRoles #175 started
          Images-AminateAllRoles #175 completed 
          Start Integration Pipeline
          Schedule job Images-IntegrationPipeline
          Build Images-IntegrationPipeline #177 started
          Images-IntegrationPipeline #177 completed  : FAILURE
          

          :

          Relevant Groovy from the main flow
          tests = parallel (
            { build("Images_API-Tests", GIT_BRANCH: git_branch ) },
            { build("Imageserver_Tests", GIT_BRANCH: git_branch ) }
          )
          
          build("Images-AminateAllRoles"  )
          
          out.println "Start Integration Pipeline"
          
          integration_build = build("Images-IntegrationPipeline", GIT_COMMIT: git_rev, GIT_BRANCH: git_branch  )
          

          Is there any other debug information I can provide to help get this fixed?

          robsweet added a comment - I'm seeing the same thing. More information: I have a build flow for a Pipeline and the way things are working right now, Images Pipeline wraps two parallel regular jobs, the Images-AminateAllRoles flow, and the Images-IntegrationPipeline flow. The build graph shows the first two parallel jobs, Images-AminateAllRoles and it's child jobs, and then stops. As you can see from the console output, it does run the second buildflow job. Job Output Building Images pipeline with Git revision b778caff96c672f2ab7a03615b68ab429a7fa279 of master parallel { Schedule job Imageserver_Tests Schedule job Images_API-Tests Build Images_API-Tests #369 started Build Imageserver_Tests #154 started Imageserver_Tests #154 completed Images_API-Tests #369 completed } Schedule job Images-AminateAllRoles Build Images-AminateAllRoles #175 started Images-AminateAllRoles #175 completed Start Integration Pipeline Schedule job Images-IntegrationPipeline Build Images-IntegrationPipeline #177 started Images-IntegrationPipeline #177 completed : FAILURE : Relevant Groovy from the main flow tests = parallel ( { build( "Images_API-Tests" , GIT_BRANCH: git_branch ) }, { build( "Imageserver_Tests" , GIT_BRANCH: git_branch ) } ) build( "Images-AminateAllRoles" ) out.println "Start Integration Pipeline" integration_build = build( "Images-IntegrationPipeline" , GIT_COMMIT: git_rev, GIT_BRANCH: git_branch ) Is there any other debug information I can provide to help get this fixed?

          Rainer Frey added a comment - - edited

          Visualizing secondary flows seem to work as long as all flows are executed in parallel:

          Parallel Flows do visualize
          parallel(
           { build("first.flow.job") },
           { build("second.flow.job") }
          )
          
          Sequential Flows Graph aborts after first flow
          build("first.flow.job")
          build("second.flow.job")
          

          Rainer Frey added a comment - - edited Visualizing secondary flows seem to work as long as all flows are executed in parallel: Parallel Flows do visualize parallel( { build( "first.flow.job" ) }, { build( "second.flow.job" ) } ) Sequential Flows Graph aborts after first flow build( "first.flow.job" ) build( "second.flow.job" )

            Unassigned Unassigned
            pedro pedro cardoso
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: