[JIRA] (JENKINS-15780) Plugin says provided key doesn't exist in file

2012-11-09 Thread jmbou...@java.net (JIRA)















































jmboulos
 assigned  JENKINS-15780 to vimil



Plugin says provided key doesnt exist in file
















Change By:


jmboulos
(09/Nov/12 6:13 PM)




Assignee:


vimil



























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






[JIRA] (JENKINS-15780) Plugin says provided key doesn't exist in file

2012-11-08 Thread jmbou...@java.net (JIRA)














































jmboulos
 created  JENKINS-15780


Plugin says provided key doesnt exist in file















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


extended-choice-parameter



Created:


08/Nov/12 9:17 PM



Description:


Just spun up Jenkins on Windows; I'm coming from Hudson on Linux, so maybe I am making an amateur mistake...

I have installed my favorite Extended Choice Parameter and configured it as I was used to, but no good.  This is what I did...

Created a file on the Master node called C:\support\traders.txt.  In the file, I put:
BOXES=a,b,c

Then in Jenkins, I put the absolute path to the file, C:\support\traders.txt, in the Properties File field, and BOXES in the Property Key field.  It finds the file, but not the key value pair inside.  Error is:
C:\support\traders.txt exists, but the provided key "BOXES" doesnt exist in this property file.

Setting this up is usually pretty straight forward, so now I am wondering if there is a bug in the new version, perhaps with my version of Windows or something...

Any thoughts?




Environment:


Windows 2008 Server R2 (64 bit), Jenkins 1.489




Project:


Jenkins



Priority:


Blocker



Reporter:


jmboulos

























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