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

Generalize the notion of Steps taking over FlowNode creation

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Icon: Minor Minor
    • pipeline

      As it says here, we should generalize the notion of a Step taking over FlowNode creation. =)

      Currently, if a Step doesn't have a block as an argument, it can't execute another Step within it. There are exceptions to this - as of this moment, parallel and load - but they're explicitly whitelisted in via a variable named 'hack', which...yeah. So I'd like to try to figure out how to do this in a more general case, because then some interesting possibilities in terms of composition show up.

            Unassigned Unassigned
            abayer Andrew Bayer
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: