Ok, I'll ask the obvious question: why did setting the branches option to master not already do this? EDIT https://www.jenkins.io/doc/pipeline/steps/workflow-

Ok, I'll ask the obvious question: why did setting the branches option to master not already do this? EDIT https://www.jenkins.io/doc/pipeline/steps/workflow-scm-step/ https://www.jenkins.io/doc/pipeline/steps/workflow-scm-step/ makes it sounds like the branches option specifies which branches to monitor for changes, after which all branches are fetched. This still seems like a counter-intuitive design that doesn't fit the most common cases.