When I set an artifact to /var/lib/docker in a build job's properties, it's changed to a relative path
Never in any application should a path that starts with / be changed to a relative path. It specifically breaks making artifacts from global operating system cached files, and it also breaks reasonable expectations for relative files in a POSIX environment.
I was able to get the artifact published with a six ../ in a row, by changing the artifact path to: ../../../../../../var/lib/docker:
However the problem surfaces later during deployment:
Because of this bug, I don't see a way to use artifacts that are outside of the build directory unless they're manually moved inside it.
- create a symbolic link to an external path inside your build directory.