[JIRA] Updated: (JENKINS-1640) Environment variables not passed through to Ant tasks

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[JIRA] Updated: (JENKINS-1640) Environment variables not passed through to Ant tasks

JIRA noreply@jenkins-ci.org

     [ http://issues.jenkins-ci.org/browse/JENKINS-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Cees Bos updated JENKINS-1640:
------------------------------

    Component/s: core
                     (was: ant)

> Environment variables not passed through to Ant tasks
> -----------------------------------------------------
>
>                 Key: JENKINS-1640
>                 URL: http://issues.jenkins-ci.org/browse/JENKINS-1640
>             Project: Jenkins
>          Issue Type: Bug
>          Components: core
>    Affects Versions: current
>         Environment: Platform: All, OS: All
>            Reporter: kphawkins
>            Assignee: redsolo
>            Priority: Critical
>
> It appears that environment variables available in the Hudson configuration
> (i.e. visible in the Hudson System Information page) are NOT passed to Ant
> builds when Hudson launches a configured Ant installation.
> This does not seem intentional. Is this by design?
> For example, I declare an environment variable MYSTERY='This is a puzzler' and
> make it available in the shell by which I launch Hudson (java -jar Hudson.war)
> I add an <echo> statement in my Ant build script to print out the value of this
> env variable. When running Ant outside of Hudson, the value of MYSTERY is
> displayed properly. When running Ant inside of Hudson, the value is not
> resolved even though Hudson displays the value of MYSTERY properly in the
> Environment Variables section of the System Information page.
> This seems unexpected.
> Is this a known issue?

--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira