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

Allow task pipeline steps to take closures for improved visualization


    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • None
    • Delivery Pipeline plugin 1.0.3
      workflow-aggregator 2.1

      The task step should be allowed to take a body (closure).

      Currently, the task action can be used to label tasks within a Jenkins pipeline stage. It allows more fine grained visualization of stages in the Delivery Pipeline view rather than just having one big block visualized for the entire stage. For e.g. pipeline failures, tasks allows for better information on information radiators on what went wrong without requiring users to actively find this information through the Jenkins UI.

      The current implementation of the task step (action) does not support bodies (closures). This was due to the stage step not accepting bodies either in the workflow-aggregator plugin 2.0 which the current solution depends on.

      If the task is allowed to take a block, it allows for more logical grouping of tasks rather than just assuming a sequential progress. This should also allow the pipeline view to visualize the current progress of a particular task better than the current solution which basically just assumes the progress of the containing stage.


      Example of how it could look like:

      for the following example pipeline syntax:



            tommysdk Tommy Tynjä
            tommysdk Tommy Tynjä
            0 Vote for this issue
            1 Start watching this issue