[JIRA] [git] (JENKINS-7411) Slave environment variables are not used during Git Polling
Mark Waite resolved JENKINS-7411 as Fixed Slave environment variables are not used during Git Polling Closing the issue since the commit which fixed it was submitted over 6 months ago. Change By: Mark Waite (25/Feb/14 12:30 AM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-7411) Slave environment variables are not used during Git Polling
Mark Waite closed JENKINS-7411 as Fixed Slave environment variables are not used during Git Polling Change By: Mark Waite (25/Feb/14 12:30 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-7411) Slave environment variables are not used during Git Polling
SCM/JIRA link daemon commented on JENKINS-7411 Slave environment variables are not used during Git Polling Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/hudson/plugins/git/GitSCM.java src/test/java/hudson/plugins/git/GitSCMTest.java http://jenkins-ci.org/commit/git-plugin/c5b127f98ebc652eead68b39aa7f1c93094cbcc4 Log: [FIXED JENKINS-7411] Environment variables are in fact not used at all during expansions. This commit fixes that. As discussed in the ticket, and as done elsewhere, the standard convention is to use previous build's environment to expand polling. Also see JENKINS-19042 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-7411) Slave environment variables are not used during Git Polling
Christoph Linder
commented on JENKINS-7411
Slave environment variables are not used during Git Polling
Also: setting the tool location on the slave via environment variables is not considered during polling.
Steps to reproduce using Jenking Git Plugin 1.3.0 on Jenkins 1.510:
Set environment variable on master:
PATH_TO_TOOLS=c:\somewhere\tools
On the Slave:
PATH_TO_TOOLS=d:\elsewhere\tools
Tool-Location for default git installation: ${PATH_TO_TOOLS}/git/git.exe
During polling, jenkins always tries to execute git.exe in c:\somewhere\tools, although it is run on the slave
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
