runAffectedUnitTests -Paffected_module_detector.enable fails on CI only about affectedmoduledetector

[shobande-femi]

Can you post the out of the log file produced by the plugin?

I struggled with this issue over the past couple of days. In my case, the specifiedBranch was absent from the working tree. (I use Github Actions and it clones the repo in some sort of minimalist fashion).

My solution was to run git fetch origin develop:develop right before runAffectedUnitTests

Note: in this case develop is the specifiedBranch. Replace with whatever branch you specified.

[6hundreds]

Experienced this stuff too at Bitrise. Perhaps you are using SpecificBranchCommit configuration with branch = {yourDevelopBranch} but your PRs is not targeted to develop, but in another branch. That's was a reason for me.

[vyshas]

@6hundreds we use bitrise as well and currently trialing this plugin. So does this mean that any branches that doesn't point to the branch mentioned in specificBrancCommit config will fail from running affected tests ? Do we know if specifiedBranchCommit accepts regex?

[antwan-flinkhub]

@6hundreds yes we do have specificBrancCommit which point to develop but the PR is also pointing to develop

[joshafeinberg]

Hello, I think @shobande-femi pointed out what is probably going wrong. You need to make sure that your CI has access to the git tree that it needs. You can find a log with a more detailed error in your logFolder/logFilename

As this hasn't been updated in a few months I am going to close, please reopen or file a new ticket if you are still having issues