- Optional versions are now returned from operations that may fail.
- Fixed a bug in the cache where a null record could be dereferenced.
- Improved validation when loading build types.
#rb Zousar.Shaker
#rnx
#ROBOMERGE-SOURCE: CL 16332909 in //UE5/Main/...
#ROBOMERGE-BOT: STARSHIP (Main -> Release-Engine-Test) (v804-16311228)
[CL 16332914 by devin doucette in ue5-release-engine-test branch]
FBuildAction and the associated builder type define the exact action to be executed, including the function and its version, and the inputs referenced by hash.
#rb Zousar.Shaker
#rnx
#preflight 609cbaed7ebade00018f29c9
#ROBOMERGE-SOURCE: CL 16317116 in //UE5/Main/...
#ROBOMERGE-BOT: STARSHIP (Main -> Release-Engine-Test) (v804-16311228)
[CL 16317121 by devin doucette in ue5-release-engine-test branch]
FBuildOutput and the associated builder type define the output of a derived data build as a collection of payloads and diagnostic messages.
#rb Zousar.Shaker
#rnx
#preflight 609c0fc05b35c60001cbc2e3
#ROBOMERGE-SOURCE: CL 16304655 in //UE5/Main/...
#ROBOMERGE-BOT: STARSHIP (Main -> Release-Engine-Test) (v800-16297934)
[CL 16304661 by devin doucette in ue5-release-engine-test branch]
IBuildFunction and the associated build context types define the interface for new derived data build functions. The inputs to a build function are referenced by FBuildDefinition. This only includes the functionality required to implement and register a build function, and does not include the functionality required to execute a build starting from a build definition.
#rb Zousar.Shaker
#rnx
#ROBOMERGE-SOURCE: CL 16278733 in //UE5/Main/...
#ROBOMERGE-BOT: STARSHIP (Main -> Release-Engine-Test) (v799-16237190)
[CL 16279132 by devin doucette in ue5-release-engine-test branch]
This only includes the functionality required to create a build definition, and does not include the functionalty required to execute a build from the build definition.
#rb Zousar.Shaker
#rnx
#preflight 608cf5ef7343ea00016e58f4
[CL 16183533 by Devin Doucette in ue5-main branch]
Moved IDerivedDataCacheModule to its own header and renamed CreateOrGetDDC to CreateOrGetCache.
#rb Zousar.Shaker
#rnx
#preflight 6089d5a036afba00015c0348
[CL 16153121 by Devin Doucette in ue5-main branch]
This allows the new cache to be implemented more efficiently using the old cache backends because functionality like the corruption wrapper and key length limiter can be bypassed and the individual backends can store cache records in whatever way is most efficient for them.
The hierarchical backend may request payloads when they are not required due to incomplete tracking of backend state, and GetPayload will never fill other backends due to the inefficiency of the existing backend framework.
The filesystem backend does not cache any state in memory, which makes requests for individual payloads less efficient than if it cached a mapping of cache payload key to raw hash after the first request for a cache key.
The HTTP, S3, and pak file backends are not implemented for the new interface.
The backends do not implement ICacheStore::CancelAll() because the existing backend framework provides WaitForQuiescence to wait for completion of async requests, and the implementation of ICacheStore by those backends works with that mechanism.
The non-leaf backends (hierarchical, async put, etc.) do not update stats from the ICacheStore functions.
#rb Zousar.Shaker
#rnx
#preflight 60899f35d324590001b47517
[CL 16148296 by Devin Doucette in ue5-main branch]
