this would be quite interesting, I think this all belongs in the stage view, somehow. Having powerful APIs is useful for future visualisations as well.
Currently the stage view is more about stages (hence the name) so some ability to reduce the "noise" of steps is required (I can imagine some folk in a stage view may indeed want to see steps executing, not just a whole stage). On Sat, Mar 26, 2016 at 2:29 AM Sergei Egorov <[email protected]> wrote: > Hey Samuel, > > Yes, initially I started to use Stage View's REST API as a source. But... > It's a HAL and doesn't use or provide a way to use embedded HAL resources. > It means that I will have to make a lot of queries to load all the data I > want. Also, there were some missing parts of the data as well. > > Also, in fact, I consume standard API provided by FlowNodes, I'm just > exposing some fields which are not exposed with Stapler, and if that > annotations will be added + new Stapler (with class support) supported then > Pipeline View will consume standard REST API of the Jenkins without any > additional API at all, at least at this moment. > > Of course, we can collaborate and improve API of Stage View to make it > consumable by Pipeline View as well. > > > BR, > Sergei > > On Fri, Mar 25, 2016 at 5:19 PM Samuel Van Oort <[email protected]> > wrote: > >> Sergei, I love the visualization this provides of the pipeline DAG! >> >> One thing worth mentioning: I have been working on a >> scalable/high-performance & parallel-aware FlowAnalyzer for pipeline stage >> view that is generalized enough to assist with the data you are >> visualizing. Since the rest-api portion of stage view is available as a >> separate plugin from UI, I might suggest consuming that API or its >> extensible Analyzer algorithm to power this view. >> >> Advantages: don't have to roll your own API, get a variety of metrics on >> each FlowNode (pause/execution timing, status, executor used) and stage. >> The algorithm also scales to complex flows with thousands of nodes and >> implements caching for executed runs. Finally it supports limiting the >> number of FlowNodes returned for a stage, so one can render a subset where >> a stage contains a loop (or deeply nested blocks) returning thousands of >> nodes. >> >> Thoughts? >> >> -- -- Regards, Michael Neale (twitter: @michaelneale, skype: michael_d_neale) Cell: +61 423175597 Cofounder & Engineer @ large in CTO office. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAEuC6Lh9rMm3QNQj-LUrafDcUjO%3DUsjVOgrVKGi%3D%2BQxxh96P%3Dw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
