You are viewing a plain text version of this content. The canonical link for it is here.

Posted to general@gump.apache.org by "Leo Simons (JIRA)" <ge...@gump.apache.org> on 2005/07/07 14:42:12 UTC

[jira] Closed: (GUMP-121) gump.plugins.EnvironmentPlugin component for customizing environment variables prior to a build

     [ http://issues.apache.org/jira/browse/GUMP-121?page=all ]
     
Leo Simons closed GUMP-121:
---------------------------

    Resolution: Fixed
     Assign To: Leo Simons

Implemented in SVN revision 209595.

> gump.plugins.EnvironmentPlugin component for customizing environment variables prior to a build
> -----------------------------------------------------------------------------------------------
>
>          Key: GUMP-121
>          URL: http://issues.apache.org/jira/browse/GUMP-121
>      Project: Gump
>         Type: New Feature
>   Components: Python-based Gump
>     Versions: Gump3-alpha-4
>     Reporter: Leo Simons
>     Assignee: Leo Simons
>      Fix For: Gump3-alpha-4

>
> We should be able to "sandbox" a project build as much as possible. This includes providing a particular project with a custom set of environment variables. We need to figure out how to make that happen and what should potentially go into the environment. Maybe we could have a plugin that sets an "env" dictionary for each project and we'll then have various builder-style plugins pass that to the Popen() constructor, and maybe have other plugins modify that environment.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org