[JIRA] Commented: (CC-1026) Configure environment variables in <exec> configuration

    [ http://jira.public.thoughtworks.org/browse/CC-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_19110 ] 

Antoine Levy Lambert commented on CC-1026:
------------------------------------------

Daniel, a way to fix the unit test permanently is to add a constructor to Builder and to ExecBuilder where you pass the environment variables and use this constructor in the test. This way you are in control of the behavior of the test independently of the environment variables of the user running it.

> Configure environment variables in <exec> configuration
> -------------------------------------------------------
>
>                 Key: CC-1026
>                 URL: http://jira.public.thoughtworks.org/browse/CC-1026
>             Project: CruiseControl
>          Issue Type: New Feature
>         Environment: all
>            Reporter: Daniel Tihelka
>            Priority: Major
>         Attachments: doc_01.patch, env_01.patch, env_02.patch, env_03.patch, env_04.patch, env_05.patch
>
>
> When running custom scripts (e.g. in python with submodules), the PYTHONPATH environment variable must be set for correct import  of the packages. The variable may be set before CruiseControl is started, but it will not work for project-dependent settings - e.g. when one project requires module of a given version, while another requires different version.
> I propose patch extending the <exec /> configuration in the following way:
> <exec>
>   <!--  Defines new value or sets new value to the existing env variable -->
>   <env name="" value=""  />
>   <!--  Deletes the existing env variable -->
>   <env name="" del="true" />
> </exec>
> while the <env /> sub-element is optional.
> Both 'name' and 'value' may contain references to CC properties, and in addition, if an unresolved property ${PROP} is found in the value, and the environment contains variable named 'PROP', the unresolved property is substituted by the value of the environment variable. In this way, we can extend already existing environment variable, e.g. as:
>  <env name="PATH" value="new/path/added:${PATH}" />
> where 'PATH' exists only as environment variable, not being defined as CC property. If it is defined as the CC property, its value would be preffered and used.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.public.thoughtworks.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d