The following case:
- Repository A contains a Jenkinsfile which contains the instruction to checkout the repository B. => When Jenkins will checkout the repository B, the plugin will try to sent a notification to the repository A with the last commit hash of the repository B, which it leads to an error.
It can be explained by the fact that the plugin will send a notification whenever a checkout is done, there is no repository check while it should only ever notify the repository that is the origin of the job trigger.
Update: It is explained by the fact the plugin relies on the GitBuildData to retrieve the commit SHA-1, however we can have several GitBuildData for a same build.