Build queue optimizer seems to ignore custom configuration parameter set in trigger(s)?
We have builds that differ only by distinct configuration parameters (e.g. PLATFORM).
The configuration parameter is set in the build customization tab of the trigger.
When two triggers fire, but with distinct configuration parameter, the second build will incorrectly get optimized away from the queue.
The only solution is probably to uncheck “Queued build can be replaced with a more recent queued build”. Unfortunately that implies that multiple builds with the same configuration parameters can pile up.
Is there any solution for this?
Please sign in to leave a comment.
Thank you for reporting this. Builds with different custom parameter values should normally remain separate in the queue. Please share your TeamCity version and the affected build configuration and trigger settings, including Build Customization, so we can investigate.
If each trigger event should build all target platforms, consider using the Matrix Build feature. You can define `PLATFORM` as a matrix parameter and use a single trigger to generate separate builds for each platform.
If the platforms need to be triggered independently, separate build configurations based on a shared template would allow queue optimization within each platform while keeping the build steps centrally maintained.
Disabling “Queued build can be replaced with a more recent queued build” remains a temporary workaround, though it may allow duplicate builds to accumulate.
We are running TeamCity version 2026.2 (238924).
How can I share the settings privately?