[JIRA] [p4-plugin] (JENKINS-25671) P4 plugin not expanding ${NODE_NAME}

[pal...@perforce.com (JIRA)]

Paul Allen
 closed  JENKINS-25671 as Fixed


P4 plugin not expanding ${NODE_NAME}
















Fixed in 1.1.3





Change By:


Paul Allen
(30/Jan/15 1:47 PM)




Status:


Open
Closed





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/d/optout.

[JIRA] [p4-plugin] (JENKINS-25671) P4 plugin not expanding ${NODE_NAME}

[g...@barefootnetworks.com (JIRA)]

Glen Gibb
 commented on  JENKINS-25671


P4 plugin not expanding ${NODE_NAME}















Hi Paul,

The job is being executed on a slave. (The job is not allowed to run on the master as the master's Linux distro is incompatible with some of the job's build tools.) And yes, it's a Freestyle job.

It should be okay to use the master and it's node name for polling.



























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/d/optout.

[JIRA] [p4-plugin] (JENKINS-25671) P4 plugin not expanding ${NODE_NAME}

[pal...@perforce.com (JIRA)]

Paul Allen
 commented on  JENKINS-25671


P4 plugin not expanding ${NODE_NAME}















Hi Glen,

Was the build executed on a Slave or the Master?  Do you see ${NODE_NAME} get expanded in either case?
I presume this is a FreeStyle or Maven Job and not a Matrix build.

${NODE_NAME} is kind of hard to evaluate during polling.  Polling often gets executed on the master despite the build being pinned to a slave.  The old logic looked at the previous build, but this seemed dangerous as the last build might not exist or the configuration could have changed.

I will need to explore Jenkins and see if I can determine it's value or perhaps default to 'master' for polling?



























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/d/optout.

[JIRA] [p4-plugin] (JENKINS-25671) P4 plugin not expanding ${NODE_NAME}

[g...@barefootnetworks.com (JIRA)]

Glen Gibb
 created  JENKINS-25671


P4 plugin not expanding ${NODE_NAME}















Issue Type:


Bug



Assignee:


Unassigned


Attachments:


config.xml, scm-polling.log



Components:


p4-plugin



Created:


18/Nov/14 6:51 PM



Description:


A project of mine uses the following workspace format: jenkins-${NODE_NAME}-${JOB_NAME}

The p4-plugin (or something higher up the stack) is not expanding the NODE_NAME variable. I see the following in my scm-polling.log file:

P4: Polling with client: jenkins-NODE_NAME-project-gold
P4: Unable to fetch changes:java.lang.NullPointerException



Attached are the project's config.xml file and the scm-polling.log file.




Environment:


Jenkins 1.590

p4-plugin 1.0.21




Project:


Jenkins



Priority:


Minor



Reporter:


Glen Gibb

























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/d/optout.