If it's a local build, it's the path where your source files are right now. (And you want the full path since you might be working with multiple versions concur

If it's a local build, it's the path where your source files are right now. (And you want the full path since you might be working with multiple versions concurrently or you might have sent someone/somewhere a locally built binary and got a core back.) If it's a CI build, I recommend exporting source files to NAS, and define a retention policy. If the org is averse to NAS despite this use case being fine and not exposing the weaknesses of NAS, you could define the absolute path as /local/commit-id/whatever and have a system where the source gets closed there relatively easily. Note that either way CI needn't build with source at the path you refix to at the post link step, and with NAS it definitely shouldn't since for this use case NAS is very bad.