Jenkins triggered by multiple git repos
I would be inclined to use Pipeline Templating as this gives you the ability to define standard templates centrally but leave the SCM field to be defined by the individual job.


  Leveraging templates in this way lets you separate the business logic (what should happen when) of your pipeline from the technical implementation (what’s actually going to happen). The result of this is a CI/CD pipeline that’s proven to be significantly easier to manage when supporting multiple teams simultaneously.


I recommend that you do not have a single pipeline for all repositories as that is going to make it very hard to tell which repository is failing or slow via dashboards and alerts.