Hi again, I'm sorry but I'm really struggling to understand this issue.
By branch history I mean your git commit history on the related branch, which just mean a list of commits like the screenshot I shared above.
> Suppose there is a repository that includes mixed sources [...] can it happen?
As of right now, multiple Bitbucket Server branch sources is unsupported behaviour, and I cannot make any guarantees of it functioning correctly. I don't have any advice to provide on multiple branch sources, and I recommend opening a feature request if that is functionality you need from the plugin so I can investigate further.
> If one of these jobs is configured to check out repository sources - should we presume the latest commit of that repository certainly relates to the functionality implemented in this job
I'm sorry but I just don't understand what this question means. It sounds like you're expecting the latest commit of your repository to somehow reflect or otherwise relate to your job configuration. If you're asking if your Jenkinsfile should be the same as the one that you draw from source, then yes. We always take the Jenkinsfile for a branch source from the same commit.
> This build notification has no relation to mentioned commit
This is what I need clarification on. What do you mean by "related to" a given commit? What precisely are you expecting that you're not seeing?
hi whitefluffypenguin , can you please share more information like the build type you have used when you encountered the issue and the reproduction steps for this?