
| Key: |
QB-1405
|
| Type: |
New Feature
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Michal Muszynski
|
| Votes: |
8
|
| Watchers: |
1
|
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 08/Oct/12 03:40 PM
Updated: 13/Jan/17 02:02 PM
|
|
| Component/s: |
None
|
| Affects Version/s: |
4.0.64
|
| Fix Version/s: |
7.0.0
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
Environment:
|
SLES Linux 11 64-bit
|
|
|
We'd like to see an option to make all configuration's variables "local". By local I mean hardcoding currently inherited variable values and disabling inheritance.
This feature would be very helpful when someone wants to archive a configuration. For example: project X is complete and in sustaining phase. I want to move obsolete configuration from root/projectX/confY to root/ARCHIVE/confY. But because this configuration may be needed in one year from now I want to make sure that it will run properly even if variables defined in root configuration change in the meantime.
Also, I think that to achieve that steps should be "freezed" too, not inherited from root configuration.
|
|
Description
|
We'd like to see an option to make all configuration's variables "local". By local I mean hardcoding currently inherited variable values and disabling inheritance.
This feature would be very helpful when someone wants to archive a configuration. For example: project X is complete and in sustaining phase. I want to move obsolete configuration from root/projectX/confY to root/ARCHIVE/confY. But because this configuration may be needed in one year from now I want to make sure that it will run properly even if variables defined in root configuration change in the meantime.
Also, I think that to achieve that steps should be "freezed" too, not inherited from root configuration. |
Show » |
| There are no comments yet on this issue.
|
|