[
https://issues.jenkins-ci.org/browse/JENKINS-11790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
gbois closed JENKINS-11790.
---------------------------
Resolution: Incomplete
Without job configuration as input, I can't try to reproduce it.
I'm closing the issue.
> Script executed by PostiBuildScript plugin is unable to use Environment
> variable defined in Jenkins
> ---------------------------------------------------------------------------------------------------
>
> Key: JENKINS-11790
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11790
> Project: Jenkins
> Issue Type: Bug
> Components: postbuildscript
> Affects Versions: current
> Environment: OS - Linux, Jenkins Running in Tomcat 7.
> Reporter: Parmendra Tyagi
> Assignee: gbois
> Attachments: Environment.png, PerforceSetting.png
>
>
> We have configured a job with "Perforce" as source code management, where we
> haven't defined the depot setting (In this case it is picking perforce
> setting from environment variable). This is working fine.
> Problem has started when i configured a script on PostBuildScript. This
> script do some checkin on perforce after build. This script is not working
> when executing under Jenkins while i am able to use same script from the
> console.
> Here is error -
> Perforce client error:
> Connect to server failed; check $P4PORT.
> TCP connect to perforce:1666 failed.
> connect: perforce:1666: Connection refused
> Perforce client error:
> Connect to server failed; check $P4PORT.
> TCP connect to perforce:1666 failed.
> connect: perforce:1666: Connection refused
> Value for P4PORT environment variable using by this script (perorce:1666 as
> shown in logs) and set value in Jenkins are different.
> That mean PostBuildScript doesn't pass the environment variable to script
> which it execute.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
