multiscm plugin - mark a repository as primary?

[James Gray]

Hi all,

I'm creating builds in Jenkins with the Job DSL plugin. This looks at my repository (Stash) and creates build configuration for that repository based on its name. At the moment, I have it so that every build pulls in two git repositories with the multiscm plugin. I keep my Jenkins utility scripts (push to artifactory stuff etc) in one repository and the other repository is the code for that project, so the utility scripts perform actions on the code repository essentially. 

The problem I have at the moment is that I have setup my repository to notify jenkins when there is a commit to one of my repositories. This means that every time I commit to my utility scripts repository, EVERY build is triggered. This seems to be a limitation of how the notification mechanism works within Jenkins. Are there any workarounds? Can I perhaps mark a repository in multiscm as a trigger repository or such?

Thanks in advcance,

James