| << Back to previous view |
|
[QB-32] Be able to inherit and override environment variables through the configuration hierarchy tree
|
|
| Status: | Closed |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor |
| Reporter: | Robin Shen | Assigned To: | Robin Shen |
| Resolution: | Fixed | Votes: | 3 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Description |
|
I'd like to be able to inherit environment variables across configurations, just like I do for variables. It's normal to have a single set of JAVA_HOME, ORACLE_HOME etc set for a whole tree (e.g. set of builds), and I found it tedious to have to add explicit environment variables to every builder I created (although I did use ognl expressions to get the actual value to set from a variable, so it's easy to change a path). If you allowed env vars to be defined/inherited, and implicitly set on all builders, then this would be much easier. Each builder could have the option to add their own env vars (obviously), and I could see that it *might* be useful to have a builder checkbox that allowed that builder to not inherit parent env vars.
|
| Comments |
| Comment by Don Ross [ 10/Mar/15 06:04 PM ] |
| I think I found a way to accomplish this in the current 6.0 implementation. If I define an environment variable in the 'master' step (or in any composition step) then that environment variable should be inherited and used by all execution steps below it. At least this is how it appears in the documentation. Can you confirm? |
| Comment by Robin Shen [ 10/Mar/15 11:30 PM ] |
| Yes they will be inherited by all build steps (command line, ant, maven, etc). |
| Comment by Don Ross [ 31/Mar/15 02:34 PM ] |
| In that case, I believe this may be resolved? Or do you have a better solution in mind down the road? |
| Comment by Robin Shen [ 01/Apr/15 12:59 AM ] |
| Yes, this should be marked as fixed. Thanks for remind. |