| Mark Waite Unfortunately the multi branch pipelines are not a good substitute for the use case we need since they pretty much create a separate 'job' per branch, which in turn is causing scaling issues on the master with git repos that have hundreds of branches, even if we filter the branches. They are definitely not ideal for manually triggered jobs with input parameters from users. We do use them for our CI and Pull Requests workload, but not for the other types of jobs we use for various other tasks. Can you clarify how users can narrow the selection during the checkout command? We tried to set the ref-spec to +refs/heads/$BRANCH:refs/remotes/origin/$BRANCH but variables do not get expanded (there is a separate Jira for this) and that variable usually starts with origin/ which would make crafting the refspec a problem anyways. |
