-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Binary pathing doesn't work for mixed builds #100
Comments
I came here to post exactly the same issue :-) I got it working locally by switching all occurrences of |
@roblundiehill-plutoflume we'd like to look into the option to specify the path (directory or full path -- not sure) with a good default value. Would that be suitable for your needs? |
I authored the original #99. An option to specify the caching path would be useful. I see a few options that are not mutually exclusive:
Unsurprisingly, I noticed that the CCI docs contain this warning:
|
From #99:
The home directory varies across CI docker images. In CircleCI-provided convenience images, the user is
circleci
and therefore the home directory is/home/circleci
. However, on many docker images, the user might beroot
and use/root
as a home directory.The problem is that the orb currently uses
~
in all its paths, even for commands that may run on different images. As a result,download_be_executables
andsave_be_cache
write binaries to and cache them from~/project/bin
. Later, commands that try to use these binaries, likewith_job_span
, also look in~/project/bin
. But if the home directory differs between the image that cached the binaries and the one that restores the cache and tries to use them, the latter will fail to locate the binaries. For example, if the image that tries to use the binaries uses theroot
user, I observe the following error:The text was updated successfully, but these errors were encountered: