|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 21/Aug/14 09:34 AM
Updated: 21/Aug/14 09:34 AM
|
|
| Component/s: |
None
|
| Affects Version/s: |
5.1.15
|
| Fix Version/s: |
None
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
Environment:
|
This issues affects version 5.1.15 but is also likely to affect all currently released versions
|
|
|
1- Create a configuration ConfA
2- Create a configuration ConfB
3- Modify ConfB to query for a parameter (Param1) when run.
4- Modify ConfA to trigger ConfB and pass across a value for Param1.
5- When you next run ConfB manually you will see that the value for Param1 has not persisted.
It should be possible to persist the value for Param1 between builds even if the build was triggered by another configuration.
Possible solution:
Add a checkbox to each variable definition that allows the user to configure if the parameter value should be persisted between builds when the build is triggered by another configuration.
|
|
Description
|
1- Create a configuration ConfA
2- Create a configuration ConfB
3- Modify ConfB to query for a parameter (Param1) when run.
4- Modify ConfA to trigger ConfB and pass across a value for Param1.
5- When you next run ConfB manually you will see that the value for Param1 has not persisted.
It should be possible to persist the value for Param1 between builds even if the build was triggered by another configuration.
Possible solution:
Add a checkbox to each variable definition that allows the user to configure if the parameter value should be persisted between builds when the build is triggered by another configuration. |
Show » |
| There are no comments yet on this issue.
|
|
New Feature
Open
Major
Remember variables passed to triggered builds