Read-only Editor deployment has project build issues (UBT/UBA)

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]

Steps to Reproduce
Execute `/path/to/RunUBT.sh TestProject Linux Development -Project=/path/to/TestProject.uproject" within a GitLab runner (a docker container with the Engine mounted read-only). See Description for further details, including what seems to be an issue with 5.8.1’s “UBA Detour” system.

Separately, any attempt of creating a Blank C++ UProject will fail to compile if the engine is read-only (file permissions, not the mount).

[Attachment Removed]

The issue regarding build_log_error_3.log seems to be resolved with a nuke of various Intermediate directories & dropping symlinked directories, and we’re seeing less build_log_error_2.log issues as well. It seems like at some point after 5.6.1, UBT became stricter around symlinks.

The issue around the read-only mount of the Engine still is a problem, however.

[Attachment Removed]

I don’t think you can mount engine to a read-only drive and then compile unless you force the Engine intermediate folders to be somewhere else… I don’t know how that works with editor builds. Will send a link to this thread to a colleague.

Regarding UBA stuff, I think above needs to be solved first.. since the uba errors seems to be related to the intermediate folder as well.

[Attachment Removed]

I see - we managed to mount the engine read-only for all of our 5.6.1 builds, so we’re curious if there’s some kind of config that would allow us to handle this. Separately, we found that UBA’s session directory creation doesn’t properly handle NFS mounts, as the timestamp comparison on creation time fails due to latency, so we’ve sorted out a number of build issues by first setting UBA_ROOT to a local tmp path.

[Attachment Removed]

Sorry for the late answer, this was flying under the radar.

Have you figured this out? If not, can you test latest binaries, and if they still don’t work then I would like to try to figure this one out with you… or if you have a fix I can look into bringing it back. thanks

[Attachment Removed]

Hi Henrik,

No worries - we ended up mounting an overlay FS on top of the read-only mounted Engine, which seemed to solve our problem in the meantime. We haven’t upgraded to 5.8.3, and probably will jump straight to 5.8.4 when it drops.

[Attachment Removed]

Perfect, thank you :slight_smile:

[Attachment Removed]