Unreal Engine Support Plugin: builds are incorrectly marked as failed to start when using Distributed BuildGraph builds

Symptoms

When using distributed build mode with the Unreal Engine Plugin in TeamCity the "parent" build can be incorrectly marked as "failed to start" if one of the builds generated by the BuildGraph output fails. Users expect the build to be marked as "failed", not as "failed to start".

This confusion in the build status indication is causing problems in viewing the trend data, as builds marked as "failed to start" do not show up in the trends view. This makes it difficult to visualize the history of failing tests. Users cannot control the dependency settings for the automatically generated configs.

Cause

The Unreal Engine Plugin generates sub-configurations at runtime, sets up the dependency settings, and handles build statuses dynamically. As a result, users cannot change these settings. This seems to be the root cause of the problem. Specifically, the dependency setting is set to "mark the build as failed to start" as default if one of the dependent builds fails, which is incorrect. This is likely a bug in the Unreal Engine Plugin.

Resolution

An issue is opened in TeamCity's bug tracking system - Unreal Engine Support: failing BuildGraph Distribute Mode builds mark the main build as Failed To Start . Users can vote for the request, leave comments, and subscribe to the updates.

Please continue to monitor the bug tracker for progress updates. If this issue is causing significant inconvenience, consider using a different configuration or approach that doesn't rely on the impacted feature until a permanent solution is provided.