I am using a single Java specs repository for a project with multiple plans. The project specs as well as the plan specs are all in that same repository.
Before this we were using YAML specs, each spec being stored in a separate repository. When a change in our flow was needed, we needed to make a pull request in many repos, which I hated, so I thought I would hold all specs in the same repo and I could also reuse common code in multiple specs.
Anyway, now I want to trigger a build in their respective plans, when a change is made in their respective specs or in the common section.
https://confluence.atlassian.com/bamkb/how-to-configure-bamboo-plans-to-be-triggered-by-specific-repository-directories-1283494292.html
When working with YAML specs, I was configuring bitbucket server repositories in my spec, due to this:
https://jira.atlassian.com/browse/BAM-21066.
Now, with Java specs, I can override the branch of the linked repo from the spec definition, so I'm using this: linked repositories. The issue is that it seems that I cannot override the change detection options per spec. Or, at least, I don't know how.
So this is what I'm asking. Is it possible, via the Java api, to override the change detection options for a linked repository so that, in different plan specs, I can have different rules for triggering a build? Or should I go back to manually defining git or bitbucket-server repos.?
