[JIRA] (JENKINS-60041) P4: Task Exception: Can't find bundle for base name org.jenkinsci.plugins.p4.Identifier, locale en_US

36 views
Skip to first unread message

ken@iliumsoft.com (JIRA)

unread,
Nov 4, 2019, 11:21:02 AM11/4/19
to jenkinsc...@googlegroups.com
Ken Morse created an issue
 
Jenkins / Bug JENKINS-60041
P4: Task Exception: Can't find bundle for base name org.jenkinsci.plugins.p4.Identifier, locale en_US
Issue Type: Bug Bug
Assignee: Unassigned
Components: p4-plugin
Created: 2019-11-04 16:20
Environment: Windows 10, Jenkins 2.190.2 (LTS)
Priority: Blocker Blocker
Reporter: Ken Morse

Since around plugin version 1.10.5, get the following when using Perforce as Source repository:

P4: builds: 35908 
P4: Connection retry: 1
Can't find bundle for base name org.jenkinsci.plugins.p4.Identifier, locale en_US
ERROR: P4: Task Exception: Can't find bundle for base name org.jenkinsci.plugins.p4.Identifier, locale en_US

 

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

kwirth@perforce.com (JIRA)

unread,
Nov 4, 2019, 12:37:02 PM11/4/19
to jenkinsc...@googlegroups.com
Karl Wirth commented on Bug JENKINS-60041
 
Re: P4: Task Exception: Can't find bundle for base name org.jenkinsci.plugins.p4.Identifier, locale en_US

Hi Ken Morse - Can you please try creating a new freestyle job that just does an SCM sync from Perforce and see if the same error occurs. If it does please send me the full console log and a screen shot showing the SCM configuration.

ken@iliumsoft.com (JIRA)

unread,
Nov 4, 2019, 2:05:02 PM11/4/19
to jenkinsc...@googlegroups.com

ken@iliumsoft.com (JIRA)

unread,
Nov 4, 2019, 2:05:03 PM11/4/19
to jenkinsc...@googlegroups.com
Ken Morse commented on Bug JENKINS-60041
 
Re: P4: Task Exception: Can't find bundle for base name org.jenkinsci.plugins.p4.Identifier, locale en_US

Sure, Karl Wirth – log of brand new Freestyle job below and screenshot attached.

 

Started by user Ken
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on buildvpc10 in workspace E:\WinPC\Main\p4test
(p4):cmd:... p4 login -s
p4 login -s
User p4dti-replicator0 ticket expires in 8 hours 40 minutes.
(p4):stop:3
(p4):cmd:... p4 client -o BuildMachine-Perforce-Test
p4 client -o BuildMachine-Perforce-Test
(p4):stop:4
(p4):cmd:... p4 counter change
p4 counter change
(p4):stop:5
(p4):cmd:... p4 changes -m1 -ssubmitted //BuildMachine-Perforce-Test/...
p4 changes -m1 -ssubmitted //BuildMachine-Perforce-Test/...
Change 34054 on 2014/03/05 by Ken@Ken_Viper_P4Test 'Test change 2 of 2.
'
(p4):stop:6
(p4):cmd:... p4 counter change
p4 counter change
(p4):stop:7
(p4):cmd:... p4 changes -m1 -ssubmitted //BuildMachine-Perforce-Test/...@33054,34054
p4 changes -m1 -ssubmitted //BuildMachine-Perforce-Test/...@33054,34054
Change 34054 on 2014/03/05 by Ken@Ken_Viper_P4Test 'Test change 2 of 2.
'
(p4):stop:8
P4: builds: 34054 
P4: Connection retry: 1
Can't find bundle for base name org.jenkinsci.plugins.p4.Identifier, locale en_US
ERROR: P4: Task Exception: Can't find bundle for base name org.jenkinsci.plugins.p4.Identifier, locale en_US
Finished: FAILURE

 

 

pallen@perforce.com (JIRA)

unread,
Nov 5, 2019, 5:15:02 AM11/5/19
to jenkinsc...@googlegroups.com

The error suggests that Identifier.properties is not in your class path; I can verity that we ship the properties file in the p4.hpi file.

unzip p4.hpi
cd WEB-INF/lib/
unzip p4.jar
ls org/jenkinsci/plugins/p4/Identifier.properties 

From the log is seems that the issue occurs on a Windows slave 'buildvpc10' perhaps the slave.jar is old? or a localisation setting has changed the class path?

 

Please can you verify this by running the job on the master or a different slave.

Perhaps redeploying the Jenkins slave may solve the issue?

kwirth@perforce.com (JIRA)

unread,
Nov 5, 2019, 5:59:03 AM11/5/19
to jenkinsc...@googlegroups.com

In addition to Paul's comments above note that I have installed 2.190.2 and P4Plugin 1.10.6 and I cannot reproduce the errors above on my Windows 10 build slave that runs Oracle Java version "1.8.0_77".  The slave is started manually with 'java -jar agent.jar -jnlpUrl http://jenkins21902:8080/computer/Windows10_Manual/slave-agent.jnlp -workDir "" '.

ken@iliumsoft.com (JIRA)

unread,
Nov 5, 2019, 9:42:03 AM11/5/19
to jenkinsc...@googlegroups.com

I got suspicious that maybe the Jenkins cache (%USERPROFILE%\.jenkins\cache) had become corrupt so I deleted the folder and restarted the agent. That completely corrected the problem reported. I can't say why this happened in the first place or why the P4 plugin was singled out, but all seems well now. Thank you Paul Allen and Karl Wirth.

pallen@perforce.com (JIRA)

unread,
Nov 6, 2019, 5:15:02 AM11/6/19
to jenkinsc...@googlegroups.com
Paul Allen closed an issue as Cannot Reproduce
 

Issue resolved.

Change By: Paul Allen
Status: Open Closed
Assignee: Paul Allen
Resolution: Cannot Reproduce

kwirth@perforce.com (JIRA)

unread,
Nov 6, 2019, 1:34:04 PM11/6/19
to jenkinsc...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages