Different behaviour between CI and local machine about affectedmoduledetector

[joshafeinberg]

Unfortunately we don't have the ability to support working on each CI. If you need to use ForkCommit you need to work with your CI to make sure all branches are pulled that are required. You can see in this file (https://github.com/dropbox/AffectedModuleDetector/blob/e4e80174988ca64ef7cf2b840a34801de0aade94/affectedmoduledetector/src/main/kotlin/com/dropbox/affectedmoduledetector/commitshaproviders/ForkCommit.kt) how we detect the parent branch and you just need to ensure your CI can pull it

Please let us know if you find any issues with the ForkCommit process but I will be closing this as like I stated, we do not have the bandwidth to support all our users CI platforms

[Evleaps]

I investigated this problem.
As I use specifiedBranch = "origin/dev" and compareFrom = "SpecifiedBranchCommit" my branch on ci always comparing with latest version "origin/dev". I using fetch dev on my CI for solve this problem.

Hence, when we push a new commit the CI compares your commit with updated develop, but other developers in your team already changed the develop branch and you can see more affected modules than you really affected.
Time is important. The count of the developers is important.

How to fix it?
You can call git merge origin dev:dev before running the pipeline. It will be working and after this, u will see only your affected modules in affected_module_detector.log. But this way might be is not cool:

• Because u will get some problems with epic branches.
• Also, u will get an extra merge commit every time when u push a new commit.

Hence, I suppose that might be better to use another compareFrom variant like ForkCommit. It works perfectly on a local machine, but I got an error on my CI.

* What went wrong:
Could not evaluate onlyIf predicate for task ':cargo:common:testReleaseUnitTest'.
> Parent branch not found

@joshafeinberg, can you or your colleagues help with the wrong. How can I use ForkCommit on my CI?