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

takesImplicitBlockArgument Step Fails without Body

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Blocker Blocker
    • workflow-cps-plugin
    • None

      A step descriptor that returns true from takesImplicitBlockArgument now requires a body.
       
      The API states:
       
      Return true if this step can accept an implicit block argument. (If it can, but it is called without a block, StepContext.hasBody() will be false.)
       
      Steps should not require bodies that are implicit/optionally indicated.
       
      This was introduced in this PR
       
      (Marked as Blocker because it has explicitly broken a stated API)

          [JENKINS-65646] takesImplicitBlockArgument Step Fails without Body

          Bryan Stopp added a comment -

          I went looking through the original PR that added this failure state. Maybe i don't understand, but I can't find any reason that this change was made.

          Bryan Stopp added a comment - I went looking through the original PR that added this failure state. Maybe i don't understand, but I can't find any reason that this change was made.

            Unassigned Unassigned
            stopp Bryan Stopp
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: