History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: CIB-612
Type: New Feature New Feature
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: jason
Reporter: Binyan
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Pulse

Support existing environment variables in resource definitions.

Created: 07/Sep/06 07:20 PM   Updated: 02/Nov/06 08:10 AM
Component/s: Build core
Affects Version/s: 1.1.9
Fix Version/s: 1.2.2

Issue Links:
Related
This issue is relates to:
CIB-613 Record the execution environment stat... Major Resolved
 


 Description  « Hide
Java properties handles most things but there are a couple things where we need to set/change the environment before a build is running. The classic case is to execute a build with java 1.4 and java 5. We need to be able to specify a set of environment variables that will be created before the build process starts.

The environment variable in "name=value" format.

Environment variables values may contain references to existing values in the following format: "name=${env.<NAME>};value". If the value of the <NAME> variable is "value2" in the current environment, then the above example will be expanded to: "name=value2;value". Using this technique, it is possible add an entry to PATH in the following manner: "PATH=my/path/entry;${env.PATH}. Case is significant even on Windows systems.

The above description was copied from our current tool which supports this.

 All   Comments   Change History      Sort Order:
Binyan - 07/Sep/06 08:52 PM
This issue can be closed. I hadn't seen resources in the agent tab when I created it.

Daniel Ostermeier - 08/Sep/06 02:23 AM
Hi Binyan,

Yes, the resources allow you to modify the execution environment of the build.

However, these resources need to be explicit. They do not support other resource or environment references. For example, you can not use the ${env.PATH} in the example above.

What should happen is that any referenece to an existing resource or an environment variable via the ${...} syntax should be resolved at the time of execution of the build. The details of the actual values used should be recorded as part of the bulid artifacts.

This is something that we intend to fix in the next major release of pulse, 1.2.

Regards,
-Daniel

Daniel Ostermeier - 08/Sep/06 02:25 AM
Scheduling this improvement for 1.2. This is more than a quick fix and so will not go into the current 1.1.x release since it is not in bug fix mode.

jason - 02/Nov/06 08:10 AM
Implemented in change 2467.