We have a GitLab runner that executes a build of our Plugins as a part of our CI system. For 5.6.1, we had no issue with the fact that the Engine was mounted as a read-only filesystem for the runner (via docker).
However, for 5.8.0 & 5.8.1, we have an issue where it tries to write to the Engine, and from our digging, we haven’t found a way to stop it from doing so. It doesn’t look like bUsePrecompiled is respected, nor does it seem to check IsEngineInstalled(), or test if the Engine directory is writable.
In 5.8.0, we’re able to build as a regular user with read-only access to the Engine. Our filesystem mount is not “read-only”, just file permissions are locked down.
However, in 5.8.1, we’re encountering what seems to be a new issue introduced in the patch. When trying to build as a regular user, the console is spammed with this:
SEE build_log_error_2.log
After much digging, we found -UBANoDetour, which allowed us to successfully compile (as a regular user, it still fails in the runner). However, as I was writing this EPS post to gather the logs from the above issue (the llvm::sys::fs::rename issue), I encountered different errors:
SEE build_log_error_3.log
---
And finally, it is not possible to create a new Blank C++ project if the Engine is read-only, as we encounter this error:
SEE cpp_project_error.log
(Apologies for the somewhat combined report, the website reloaded on me when I tried to drag & drop to attach files, so I lost that progress and had to start over)
[Attachment Removed]