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

Workflow's ExecutorStep should support searching of the node

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      We want to record the information about nodes being used by workflow.
      Currently it's difficult, because Workflow plugin does not offer extension points allowing to monitor executions and to discover executor usages.

      I propose to add a new FlowListener extension point, which allows to subscribe to workflow node status changes.

        Attachments

          Issue Links

            Activity

            Hide
            svanoort Sam Van Oort added a comment -

            Oleg Nenashev Would appreciate if you could flesh out the requirements here a bit more to be clearer what the request is – what the listener would trigger on, what information it would offer, or alternately if you wanted to fetch node info from Pipelines after the fact, what you'd want.

            Show
            svanoort Sam Van Oort added a comment - Oleg Nenashev Would appreciate if you could flesh out the requirements here a bit more to be clearer what the request is – what the listener would trigger on, what information it would offer, or alternately if you wanted to fetch node info from Pipelines after the fact, what you'd want.
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            Sam Van Oort it's ticket is 2.5 years old, and I do not longer have use-case which I had for the ticket. I think it still makes sense to have something, but whatever works

            Show
            oleg_nenashev Oleg Nenashev added a comment - Sam Van Oort it's ticket is 2.5 years old, and I do not longer have use-case which I had for the ticket. I think it still makes sense to have something, but whatever works
            Hide
            nateshkukreja Natesh Kukreja added a comment -

            Hey, this ticket would be useful for us!

            In general, we have a pipeline that generates 400+ stageFlowNodes. We have about 5 stages, each with a varying about of stageFlowNodes. In specific, we have a pipeline that spawns 48 parallel branches, each includes 8 steps, which show up as stageFlowNodes under a stage. 

            Our issue here is that we cannot query the pipeline beyond the first 100 stageFlowNodes using the workflow api (wfapi/describe) - more specifically using http://<jenkins_url>/<build_number>/execution/node/<stage_id>/wfapi/describe

             

            Using this information, we are able to extract how long each test ran. 

            I have been trying to find a way to query beyond the 100 stageFlowNodes, but have been unsuccessful - being able to see more than the first 100 would benefit us greatly.

             

             

            Show
            nateshkukreja Natesh Kukreja added a comment - Hey, this ticket would be useful for us! In general, we have a pipeline that generates 400+ stageFlowNodes. We have about 5 stages, each with a varying about of stageFlowNodes. In specific, we have a pipeline that spawns 48 parallel branches, each includes 8 steps, which show up as stageFlowNodes under a stage.  Our issue here is that we cannot query the pipeline beyond the first 100 stageFlowNodes using the workflow api (wfapi/describe) - more specifically using http://<jenkins_url>/<build_number>/execution/node/<stage_id>/wfapi/describe   Using this information, we are able to extract how long each test ran.  I have been trying to find a way to query beyond the 100 stageFlowNodes, but have been unsuccessful - being able to see more than the first 100 would benefit us greatly.    
            Hide
            nateshkukreja Natesh Kukreja added a comment -

            Oleg Nenashev, reading through this issue again, I do not believe this is exactly what we are talking about. This issue is useful to our cause, however we are asking for more information to be displayed by the workflow api. 

            Should I still wait on this ticket, or should I open a new ticket? Thanks

            Show
            nateshkukreja Natesh Kukreja added a comment - Oleg Nenashev , reading through this issue again, I do not believe this is exactly what we are talking about. This issue is useful to our cause, however we are asking for more information to be displayed by the workflow api.  Should I still wait on this ticket, or should I open a new ticket? Thanks
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            Feel free to create a new ticket if you feel they are different. Pull requests will be also appreciated

            Show
            oleg_nenashev Oleg Nenashev added a comment - Feel free to create a new ticket if you feel they are different. Pull requests will be also appreciated

              People

              • Assignee:
                Unassigned
                Reporter:
                oleg_nenashev Oleg Nenashev
              • Votes:
                3 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated: