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

Binary compatibility broken in InputStepExecution#proceed in 2.6

    Details

    • Similar Issues:

      Description

      We changed proceed(Object) to proceed(Map), but forgot it was a public method. So let's get back that binary compatibility.

        Attachments

          Issue Links

            Activity

            Show
            abayer Andrew Bayer added a comment - PR up at https://github.com/jenkinsci/pipeline-input-step-plugin/pull/15
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Andrew Bayer
            Path:
            src/main/java/org/jenkinsci/plugins/workflow/support/steps/input/InputStepExecution.java
            http://jenkins-ci.org/commit/pipeline-input-step-plugin/b29125bdea8cbaafacf5df59839e109840d5a9e2
            Log:
            [FIXED JENKINS-43856] Restore binary compatibility with pre-2.6 releases

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Andrew Bayer Path: src/main/java/org/jenkinsci/plugins/workflow/support/steps/input/InputStepExecution.java http://jenkins-ci.org/commit/pipeline-input-step-plugin/b29125bdea8cbaafacf5df59839e109840d5a9e2 Log: [FIXED JENKINS-43856] Restore binary compatibility with pre-2.6 releases

              People

              • Assignee:
                abayer Andrew Bayer
                Reporter:
                abayer Andrew Bayer
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: