
Key: |
QB-2750
|
Type: |
Improvement
|
Status: |
Closed
|
Resolution: |
Won't Fix
|
Priority: |
Major
|
Assignee: |
Robin Shen
|
Reporter: |
J. Mash
|
Votes: |
0
|
Watchers: |
0
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 28/Jun/16 05:46 PM
Updated: 03/Aug/16 06:27 PM
|
|
Component/s: |
None
|
Affects Version/s: |
None
|
Fix Version/s: |
None
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
This is a request to add a 'workspaceRoot' property to the 'node.properties' file.
The idea behind this request is to allow a means of globally defining / overriding the default workspace root for the node. This improvement would better support custom node configurations, such as having a separate drive subsystems with different backup, security, and virus scanning policies dedicated to different purposes (in our case, one drive subsystem is dedicated to the workspace). This would also allow the workspace root to be changed in one location on the node and have it apply globally with no further changes.
This can be emulated with environment variables or user attributes, but introduces a much larger maintenance concern as a result -- In this scenario, changing the workspace directory requires changing the value of the environment variable / user attribute along with *all* of the places it is referenced. This is how we currently manage it, but there have been some cases where bugs were introduced due to missing a location where the environment variable / user attribute was referenced, and in some cases remained a latent bug for many days until the node in question entered the rotation.
This seems like it would be reasonably simple to add, but provide a HUGE benefit to us in our case as we manage roughly 90 build nodes of varying drive configurations.
|
Description
|
This is a request to add a 'workspaceRoot' property to the 'node.properties' file.
The idea behind this request is to allow a means of globally defining / overriding the default workspace root for the node. This improvement would better support custom node configurations, such as having a separate drive subsystems with different backup, security, and virus scanning policies dedicated to different purposes (in our case, one drive subsystem is dedicated to the workspace). This would also allow the workspace root to be changed in one location on the node and have it apply globally with no further changes.
This can be emulated with environment variables or user attributes, but introduces a much larger maintenance concern as a result -- In this scenario, changing the workspace directory requires changing the value of the environment variable / user attribute along with *all* of the places it is referenced. This is how we currently manage it, but there have been some cases where bugs were introduced due to missing a location where the environment variable / user attribute was referenced, and in some cases remained a latent bug for many days until the node in question entered the rotation.
This seems like it would be reasonably simple to add, but provide a HUGE benefit to us in our case as we manage roughly 90 build nodes of varying drive configurations.
|
Show » |
No work has yet been logged on this issue.
|
|