[#QB-2039] Trigger configuration step records build version even if no build was triggered.

QuickBuild

Trigger configuration step records build version even if no build was triggered.

Created: 29/Apr/14 08:50 PM Updated: 01/May/14 02:31 PM

Component/s:

None

Affects Version/s:

5.1.19

Fix Version/s:

None

Original Estimate:

Unknown

Remaining Estimate:

Unknown

Time Spent:

Unknown

Description

« Hide

In reference to QR-2038 (the root cause that resulted in the trigger step failing). A trigger step set to "Respect Build Condition" and "Wait for Finish" should indicate that no build was triggered if the build condition of the configuration returned false. Instead if the condition returns false and the last completed build was FAILED/CANCELLED/TIMEOUT then the trigger step is failed too, even though it didn't trigger anything.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Robin Shen [30/Apr/14 01:12 AM]

This seems appropriate for most cases we've seen now. Normally user uses the "trigger build step" to trigger a dependency, and the master build should be failed if any of its current dependency is failed even if the dependency build is not being triggered recently. This also happens when a dependency of configuration is set up via via QuickBuild repository.

[ Permlink | « Hide ]

Robin Shen [01/May/14 02:31 PM]

Closing due to the reason commented. Feel free to reopen it if you think there is a reason for this behavior.