Horde - Incremental Workspace – Automatic Cleanup of Stale Build Artifacts

Development Pipeline & Plugins
, ,
1

Hi,

we’re running incremental build workspaces on our build farm (Horde agents) and we’re seeing gradual accumulation of stale build artifacts over time — things like orphaned intermediate files, old .obj/.lib files for modules that no longer exist, leftover DDC entries, etc.

A few specific questions:

  1. Is there any built-in option in UBT (or Horde agent configuration) to automatically detect and purge stale/unused build artifacts as part of the incremental build process — without having to schedule a full clean?
  2. Does the Horde workspace conform mechanism handle this in any way, or does it only deal with source file sync and leave build output untouched?
  3. How does Epic handle this internally — is there a scheduled cleanup job, a TTL policy on artifacts, or something baked into the stream/template config? Is any of that approach available/documented externally?

Thanks and Regards

Lubos

[Attachment Removed]

2

Hello,

We do have UBA enabled and are using it for remote compilation, split into two separate pools — one for Horde agents and one for developer machines — with no mixing between them.

However, we are not sure whether we have a UBA cache server set up. At least we don’t believe so. So yes, documentation on how to configure the cache server would be very welcome!

Also, just to make sure we understand the recommended approach correctly — would the ideal setup be to run a scheduled full conform on incremental workspaces (e.g. once a week) to clean up stale artifacts, while relying on the UBA cache server to make that conform non-destructive in terms of compile times?

[Attachment Removed]