We are trying to trigger multibranch jobs (via cloudbees-bitbucket-branch-source), and it is failing for jobs that are lower in alphanumeric order. Affected jobs' multibranch pipeline events page just shows: "No events as of Sat May 22 09:39:30 BST 2021, waiting for events..." and they do not start.
Inspecting jenkins.branch.MultiBranchProject.log shows:
Upon inspecting job36, we noticed the git repo in its config does not exist. And when we disabled this job, the "Found match ..." lines proceeded past this and processed the rest of the jobs, including the one we wanted to trigger (job40), which started successfully.
branch-api-plugin should tolerate such misconfigured jobs that have a non-existent repo, and not block jobs after it triggering. This might have also been the cause of
JENKINS-63815. We are on branch-api-plugin v2.6.3 & Jenkins v2.277.4