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

withCredentials shouldn't require a node context for all possible bindings

    Details

    • Similar Issues:

      Description

      Currently, withCredentials requires a node context to run, regardless of whether the particular binding(s) being used actually need it. Ideally, MultiBinding extensions/implementations would mark that they need a node context (i.e., for a workspace), but since it's already got a defined API, it probably makes more sense to end up marking extensions that don't need a node context, since that won't break any existing extensions. Then BindingStep.Execution can be updated to only error out if there's no node context and one or more of the Binding extensions being used need it.

        Attachments

          Issue Links

            Activity

              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: