|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 02/Aug/11 12:52 PM
Updated: 02/Aug/11 11:43 PM
|
|
| Component/s: |
None
|
| Affects Version/s: |
3.1.54
|
| Fix Version/s: |
None
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
|
Let's assume we have variable: VERSION=4 (which is in fact next build number in this example)
In next build label field we are using option "Use specified version" which is "${vars.get("VERSION").increase()}"
Now we have a step which is using value from VERSION variable. Because VERSION variable is modified in creation of the next build label, the step receives VERSION as 5 which is wrong. It should be 4 till end of build.
As workaround I can move increase to PostBuild script section but this is double work since the NBL field can be evaluated at the end of build call.
|
|
Description
|
Let's assume we have variable: VERSION=4 (which is in fact next build number in this example)
In next build label field we are using option "Use specified version" which is "${vars.get("VERSION").increase()}"
Now we have a step which is using value from VERSION variable. Because VERSION variable is modified in creation of the next build label, the step receives VERSION as 5 which is wrong. It should be 4 till end of build.
As workaround I can move increase to PostBuild script section but this is double work since the NBL field can be evaluated at the end of build call.
|
Show » |
|
Improvement
Closed
Major
next build label field should be evaluated as a final step of a configuration
${vars.get("VERSION").increase(); vars.get("VERSION");}
Then you will have the same value for current version and the "VERSION" variable.