If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 28/Jan/09 01:58 PM
Updated: 28/Jan/09 01:58 PM
|
|
Component/s: |
None
|
Affects Version/s: |
None
|
Fix Version/s: |
None
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
Environment:
|
Windows, Linux, Solaris
|
|
environment variables set when QuickBuild is launched, and also those set by tomcat to run QuickBuild, are all inherited by builders, and sometimes cause unexpected results. The env variables for builders should be limited to what is specified in the builder. This problem is discussed briefly in the forum thread link below. My ideal implementation would be having three choices as the basis for the env variables per builder: no env variables that aren't set explicitly in the builder; the basic variables like $HOME, $USER, and $SHELL; and the full login shell of the user that the build is being run by (note, this does not mean the full environment that QuickBuild has, it means if the user were to open an interactive login shell and run the builder command.
http://forum.pmease.com/viewtopic.php?f=1&t=525
|
Description
|
environment variables set when QuickBuild is launched, and also those set by tomcat to run QuickBuild, are all inherited by builders, and sometimes cause unexpected results. The env variables for builders should be limited to what is specified in the builder. This problem is discussed briefly in the forum thread link below. My ideal implementation would be having three choices as the basis for the env variables per builder: no env variables that aren't set explicitly in the builder; the basic variables like $HOME, $USER, and $SHELL; and the full login shell of the user that the build is being run by (note, this does not mean the full environment that QuickBuild has, it means if the user were to open an interactive login shell and run the builder command.
http://forum.pmease.com/viewtopic.php?f=1&t=525 |
Show » |
There are no comments yet on this issue.
|
|