[JIRA] Updated: (CC-1026) Configure environment variables in <exec> configuration
"Daniel Tihelka (JIRA)" <[email protected]> Tue, 29 Mar 2011 16:49:43 -0500 (CDT)
| Newsgroups | gmane.comp.java.cruise-control.devel |
|---|---|
| Message-ID | <125542877.1301435383554.JavaMail.root@chidmzhosting02.thoughtworks.com> |
[ http://jira.public.thoughtworks.org/browse/CC-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Tihelka updated CC-1026:
-------------------------------
Attachment: env_06.patch
The env_06.patch should solve all issues with undefined env variables - it uses ant to define a special variable used in the test (long live ant!). I have tried it under Linux (gentoo) as well as under windows XP and the test passed.
Do not also forget to apply doc_01.patch holding the documentation changes!
> 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, env_06.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
------------------------------------------------------------------------------
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software
be a part of the solution? Download the Intel(R) Manageability Checker
today! http://p.sf.net/sfu/intel-dev2devmar