Notes

Legacy Process:

In the legacy process, dispatching the "DeliverAssetToTrain" configurations required users to select the specific asset associated with each train and then provide the relevant source update. Each configuration needed to be dispatched one at a time, with a unique config selected for each train, leading to a repetitive process involving multiple configurations.


The updated process allows the train name to be entered directly as an input parameter using the ‘Destination mainline OS Train’ field in Trainline, eliminating the need to select a different configuration for each train manually. Now, users only need to select one configuration per asset, and the system will dynamically dispatch the configuration for each train using the train name parameter.


Impact:

Enhanced Performance and Reliability: This change addresses ongoing issues with online dispatch responsiveness caused by storage constraints from handling multiple configuration files. Previously, the high volume of configs led to frequent space limitations, causing delays, data loss, and requiring manual intervention to restore functionality. By consolidating to a single dynamic configuration per asset, this update minimizes overhead, reduces the likelihood of dispatch delays, and ensures a more seamless and reliable build process.


Reduced Repetition: Eliminates the need to select separate configurations for each train, reducing redundant steps in the dispatch process.


Decreased Complexity: Simplifies the process, reducing potential confusion from managing multiple configurations.


No Impact on other functions: This update does not alter how the dispatched builds are handled on build managers or how the dispatched tasks are run.