- added optional UAT parameter PackageEncryptionKeyFile to specify the encryption key file to use during packaging for supporting platforms
- example usage: -PackageEncryptionKeyFile=C:\MyProject\MyEncryptionKey.key
#rb Andrew.Firth, David.Harvey
#lockdown michal.valient
#preflight 616e13e96e12ff000113feab
#ROBOMERGE-AUTHOR: eric.mcdaniel
#ROBOMERGE-SOURCE: CL 17861698 via CL 18004085 via CL 18369956 via CL 18369989
#ROBOMERGE-BOT: STARSHIP (Release-Engine-Staging -> Release-Engine-Test) (v895-18170469)
[CL 18370000 by eric mcdaniel in ue5-release-engine-test branch]
#rb minor
#lockdown jeff.farris
#preflight 614c92f8a3efb40001bf949f
#ROBOMERGE-AUTHOR: andrew.firth
#ROBOMERGE-SOURCE: CL 17608554 via CL 17962776 via CL 18364967 via CL 18365025
#ROBOMERGE-BOT: STARSHIP (Release-Engine-Staging -> Release-Engine-Test) (v895-18170469)
[CL 18365080 by andrew firth in ue5-release-engine-test branch]
+ grepping more logs/info to debug a specific warning
#jira UE-133899
#ROBOMERGE-AUTHOR: mitchell.fisher
#ROBOMERGE-SOURCE: CL 18333705 in //UE5/Release-5.0/... via CL 18333717
#ROBOMERGE-BOT: STARSHIP (Release-Engine-Staging -> Release-Engine-Test) (v895-18170469)
[CL 18333732 by mitchell fisher in ue5-release-engine-test branch]
This change is a re-implementation of a previous fix for the same issue that was lost during the move from UE4->UE5
#preflight 619e28d3aa4521f9e7b6c0c2
#ROBOMERGE-AUTHOR: graeme.thornton
#ROBOMERGE-SOURCE: CL 18284269 via CL 18284297 via CL 18284301 via CL 18284323 via CL 18284325 via CL 18285442 via CL 18285467
#ROBOMERGE-BOT: STARSHIP (Release-Engine-Staging -> Release-Engine-Test) (v895-18170469)
[CL 18285476 by graeme thornton in ue5-release-engine-test branch]
#rnx
[FYI] chris.babcock, ryan.durand
#ROBOMERGE-AUTHOR: ryan.hummer
#ROBOMERGE-SOURCE: CL 18251049 via CL 18251050 via CL 18251051 via CL 18253556 via CL 18253570
#ROBOMERGE-BOT: STARSHIP (Release-Engine-Staging -> Release-Engine-Test) (v895-18170469)
[CL 18253583 by ryan hummer in ue5-release-engine-test branch]
- Note that for Windows to work, the AutomationTool.exe needs to be marked as a Desktop app, so when running on Linux, this command is needed one time: sed -i 's/WindowsDesktop/NETCore/' AutomationTool.runtimeconfig.json
- Removed some platform-specific checks for the platform building it, and #if WINDOWS type checks (not all gone, but getting better)
#rb jonathan.adamczewski
#preflight 6195a7de841fa7e69d5964d4
[FYI] graeme.thornton
#ROBOMERGE-AUTHOR: josh.adams
#ROBOMERGE-SOURCE: CL 18237766 via CL 18242422 via CL 18242492 via CL 18242564 via CL 18244551 via CL 18244617
#ROBOMERGE-BOT: STARSHIP (Release-Engine-Staging -> Release-Engine-Test) (v895-18170469)
[CL 18244669 by josh adams in ue5-release-engine-test branch]
#rnx
#rb trivial
#ROBOMERGE-AUTHOR: ryan.hummer
#ROBOMERGE-SOURCE: CL 18237629 via CL 18237632 via CL 18237637 via CL 18237643 via CL 18240721 via CL 18240752
#ROBOMERGE-BOT: STARSHIP (Release-Engine-Staging -> Release-Engine-Test) (v895-18170469)
[CL 18242896 by ryan hummer in ue5-release-engine-test branch]
* No longer modify the global kubecontext but rather pass the context to use into helm
* Added option to specify which kubeconfig to use
* Fixed issue when values not being handled correctly
#ROBOMERGE-AUTHOR: joakim.lindqvist
#ROBOMERGE-SOURCE: CL 18238748 in //UE5/Main/...
#ROBOMERGE-BOT: STARSHIP (Main -> Release-Engine-Test) (v895-18170469)
[CL 18238770 by joakim lindqvist in ue5-release-engine-test branch]
Also added ability to override path to dotnet for DotnetTask, to allow us to use a system install dotnet for special cases (in this case we use a newer .NET version then the rest of the engine)
#ROBOMERGE-AUTHOR: joakim.lindqvist
#ROBOMERGE-SOURCE: CL 18222416 in //UE5/Main/...
#ROBOMERGE-BOT: STARSHIP (Main -> Release-Engine-Test) (v895-18170469)
[CL 18222429 by joakim lindqvist in ue5-release-engine-test branch]
