[#QB-664] Variables carry forward on promotion

QuickBuild

Variables carry forward on promotion

Created: 07/Oct/10 02:03 PM Updated: 11/Nov/16 07:00 AM

Component/s:

None

Affects Version/s:

3.0.10

Fix Version/s:

3.0.11

Original Estimate:

4 hours

Remaining Estimate:

4 hours

Time Spent:

Unknown

Description

« Hide

Variables on promoted builds should automatically be inherited unless the configuration you are promoting to explicitly defines that variable for itself. In that case you must explicitly tag the variable to override the promotion target's configuration variable.

Promotions should carry as much information forward as possible, so you know exactly what build you are working with.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Jared Stutesman [07/Oct/10 03:05 PM]

For example:

root/config1:
defines:
var1="childVar1"
var2="childVar2"
var3="childVar3" - this variable explicitly tagged to promote

root/configTarget:
defines:
var2 = "targetVar2"
var3 = targetVar3"

when a build is promoted from root/config1 to root/configTarget it should be left with:
var1="childVar1" - this variable is automatically inherited
var2="targetVar2" - this variable is not inherited because it is defined configTarget
var3="childVar3" - this variable overrides the configTarget value because it was explicitly set to override

[ Permlink | « Hide ]

Robin Shen [10/Oct/10 04:39 AM]

This issue is now fixed in 3.0.11. However the explicit flag to carry over variable is not used for easy understanding of variable definition. To override variables already defined in destination configuration, user needs to specify the variable when define the promotion.

[ Permlink | « Hide ]

Robin Shen [30/Jul/11 01:00 PM]

Unfortunately we have to revert this change due to several feedbacks from other customers. Refer to ~~QB-996~~ for details.

[ Permlink | « Hide ]

Anais Gonzalez [05/Aug/11 06:39 PM]

We have extensive automation and configurations that depend on this functionality being present. They have been working for months and it would greatly hinder our automation process if we lost this to the point that we are now considering switching to either a different system or just stop updating Quickbuild indefinitely. Please either put that functionality back or help us by providing a patch we could use to get it back. As it stands right now, it's greatly hindering our ability to use your product.

[ Permlink | « Hide ]

Jared Stutesman [05/Aug/11 08:09 PM]

It looks like ~~QB-996~~ is referring to inheriting the variables from the configuration to be prompted on the promotion script, but ~~QB-664~~ is about inheriting the variables on the build that is being promoted to the build being triggered by the promotion. It seems to me that both things make sense and are not mutually exclusive. Am i misreading the issue or can have both functionalities?

[ Permlink | « Hide ]

Robin Shen [19/Aug/11 08:23 AM]

An option is added in promotion definition in 3.1.56 to optionally enable/disable this feature.

[ Permlink | « Hide ]

Martin [11/Nov/16 07:00 AM]

Where is this option to enable/disalbe this feature in QB 6.0? I can see only the one for prompted configuration variables