Dereferencing Bazel Runfile Symlinks 'invalid command code' error

[cjohnstoniv]

When executing the run step, this results in no blame history being found by the sonar analyzer.

At the the start of the run step a see many of these sed errors:

Dereferencing bazel runfiles symlinks for accurate SCM resolution...
sed: 1: "./git/[path] ...": invalid command code .

I am running this on a Mac OSX with bazel running as sudo. Is there something I am missing and/or have configured incorrectly?

P.S. really appreciate this project, it unlocked the door for me to justify exploring Bazel for my organization :)

[Zetten]

Hi @cjohnstoniv, I assume this is caused by a difference in the OSX sed version. I'm afraid I haven't got access to a Mac to test it, but I'm happy to accept any PR which helps fix platform issues.

Maybe you can spot an improvement in the action script (https://github.com/Zetten/bazel-sonarqube/blob/master/defs.bzl#L108).

If not, I'd perahps rewrite the action to break the symlink dereferencing out to a separate action. This could then be switchable by an attribute (since I wrote this, I discovered maybe some tags like "no-sandbox" or "local" could work around the original symlink issue). The new symlink dereferencing action could execute a configurable *_binary target, which would allow a select to choose a different script based on the current platform.