Display the full path of the defaeult prebuild sandbox

[cnadeau]

No description provided.

[daxiosreview]

⚠️	Layout/LineLength: Line is too long. [129/120]

[trinhngocthuyen]

Thanks for the MR. I wonder what lead you to this change. Was there any issue with the current implementation that we need to be aware of?

[cnadeau]

@trinhngocthuyen I was running in fastlane and I lost an hour before I realized that the _Prebuild was ignored because the prebuild command was run in the fastlane folder, not in the root of the project where the Podfile is. I would have seen it immediately if that log has been in place at that time. Nothing to report other than helping anyone getting in the same situation in the future

[trinhngocthuyen]

@cnadeau Thanks for sharing the context.

I would like to express my concern about this change:

• I understand that fastlane runs its commands in its folder which caused the issue. However, this issue is not specific to the plugin as it can happen to any other use cases. As an example, running normal pod install (without the plugin) also requires the current working dir to be in the project dir (not the fastlane dir). Running CocoaPods installation would also lead to the same issue.
• Given that, I think prepending Dir.pwd to the prebuild_sandbox_path should not fix the problem. And we need to revise many other places if we do it this way.
• What we can do in this case is to surface the issue for investigation by printing the prebuild_sandbox_path. In fact, we did print the prebuild sandbox path in https://github.com/grab/cocoapods-binary-cache/blob/master/lib/cocoapods-binary-cache/hooks/pre_install.rb#L57. But it's only visible with the --verbose option.
  --> Perhaps we can change Pod::UI.message to Pod::UI.puts, I may suggest.

Your thoughts?