paul chipchase 1a5466f3d4 Virtualization backends no longer falsely report that payloads failed to push if the default code path for batched pushing is used. ...

#rb Per.Larsson
#jira UE-141304
#rnx
#lockdown Mark.Lintott
#preflight 61fd3cccb5092d45ad18c953

- Not all backends gain from pushing payloads in batches. In this case the backend can opt not to override the default implementation which will just iterate over the batch of payloads and then push each one individually.
- However when the default path was used, FPushRequest::Status was not updated after the push was performed, which resulted in each request returning the default (failed) status.
-- The backends that use the default path are not enabled in any of our internal projects so this was not noticed.
- So even though the payloads were pushed, the virtualization process would log and error and block any submit being performed.
-- Subsequent submits of the same packages would work because we would note much earlier that the payloads are already stored in the backend and the broken code path would never run.
- Added fall through comment as required by the coding standards

#ROBOMERGE-AUTHOR: paul.chipchase
#ROBOMERGE-SOURCE: CL 18863318 in //UE5/Release-5.0/... via CL 18863334 via CL 18863548
#ROBOMERGE-BOT: UE5 (Release-Engine-Test -> Main) (v910-18824042)

[CL 18863566 by paul chipchase in ue5-main branch]

2022-02-04 10:30:52 -05:00

..

Private

Reworked IVirtualizationSystem::DoPayloadsExist to be clearer about how it works.

2022-02-04 02:41:37 -05:00

Public

Virtualization backends no longer falsely report that payloads failed to push if the default code path for batched pushing is used.

2022-02-04 10:30:52 -05:00

Virtualization.Build.cs

Give improved error messages to the user if the source control asset virtualization backend fails to connect.

2022-01-18 04:50:38 -05:00