Bitbucket legacy structure constraints.

[will martin]

New to this environment at work. Jobs (1 per uService) are grouped under a single repo. Each job references a single uService tree ("project" in local terms).

I'm looking to find a means of triggering builds for only the committed uService code. But all plugins I've come across reference a structure inverted to ours. Each uService would have its own repository.

The question is whether I should make the case to restructure the current bitbucket environment so that repos belong to projects rather than vice versa. OR, will I be able to add filters to trigger plugins such that they only select specific "project" jobs and not all jobs in the repository? I'm prepared to contribute or write new plugins, skill-wise, but don't want to invest where the community would vote anti-pattern.

Thanks

Will