-
Bug
-
Resolution: Unresolved
-
Major
-
None
In our logs I can see many lines such as the ones below:
Problem: Error in client specification. Missing required field 'Root'.
For Command: /u-blox/gallery/perforce/p4/lin_64/2014.1/bin/p4 -P CB36E3E1DC213D9D0161CA6FF7C5309B -s client -S //l1phy/main_l1phy -i
With Data:
===================
Client: main_mlb_full_split_stack_build_jenkins_mlb-2062542078
Description:
Root:
Options: noallwrite clobber nocompress unlocked nomodtime rmdir
LineEnd: local
Stream: //l1phy/main_l1phy
When looking at the client spec (see image) i can see a Root specified.
I am not sure if this is causing any problems but something must be causing this
[JENKINS-24366] Missing Root in client spec
Morne Joubert
created issue -
Morne Joubert
made changes -
| Description |
Original:
In our logs I can see many lines such as the ones below: Problem: Error in client specification. Missing required field 'Root'. For Command: /u-blox/gallery/perforce/p4/lin_64/2014.1/bin/p4 -P CB36E3E1DC213D9D0161CA6FF7C5309B -s client -S //l1phy/main_l1phy -i With Data: =================== Client: main_mlb_full_split_stack_build_jenkins_mlb-2062542078 Description: Root: Options: noallwrite clobber nocompress unlocked nomodtime rmdir LineEnd: local Stream: //l1phy/main_l1phy When looking at the client spec (see image) i can see a Root specified |
New:
In our logs I can see many lines such as the ones below: Problem: Error in client specification. Missing required field 'Root'. For Command: /u-blox/gallery/perforce/p4/lin_64/2014.1/bin/p4 -P CB36E3E1DC213D9D0161CA6FF7C5309B -s client -S //l1phy/main_l1phy -i With Data: =================== Client: main_mlb_full_split_stack_build_jenkins_mlb-2062542078 Description: Root: Options: noallwrite clobber nocompress unlocked nomodtime rmdir LineEnd: local Stream: //l1phy/main_l1phy When looking at the client spec (see image) i can see a Root specified. I am not sure if this is causing any problems but something must be causing this |
| Assignee | Original: Rob Petti [ rpetti ] |
Morne Joubert
added a comment - Hi Rob,
We are using Jenkins 1.568 on master on linux (slaves on windows and linux) , Perforce plugin 1.3.27
We upgraded to 1.3.27 (from 1.3.24) in the last 2 weeks, we have only recently noticed these errors in the log files.
I am not sure if it is related to:
hudson.plugins.perforce.utils.ParameterSubstitutionException: <${jobName}_jenkins_mlb>: Found unresolved macro at '${jobName}_jenkins_mlb'
at hudson.plugins.perforce.utils.MacroStringHelper.checkString(MacroStringHelper.java:97)
at hudson.plugins.perforce.utils.MacroStringHelper.substituteParameters(MacroStringHelper.java:64)
at hudson.plugins.perforce.PerforceSCM.getDepot(PerforceSCM.java:463)
at hudson.plugins.perforce.PerforceMailResolver.findPerforceMailAddressFor(PerforceMailResolver.java:78)
at hudson.plugins.perforce.PerforceMailResolver.findMailAddressFor(PerforceMailResolver.java:25)
at hudson.tasks.MailAddressResolver.resolve(MailAddressResolver.java:112)
at hudson.tasks.Mailer$UserProperty.getAddress(Mailer.java:547)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
...
that we saw during this period as well
It doesn't seem to be impacted the actual running of the freestyle projects but wanted to check why these are in the log files.
Morne Joubert
added a comment - Hi Rob,
We are using Jenkins 1.568 on master on linux (slaves on windows and linux) , Perforce plugin 1.3.27
We upgraded to 1.3.27 (from 1.3.24) in the last 2 weeks, we have only recently noticed these errors in the log files.
I am not sure if it is related to:
hudson.plugins.perforce.utils.ParameterSubstitutionException: <${jobName}_jenkins_mlb>: Found unresolved macro at '${jobName}_jenkins_mlb'
at hudson.plugins.perforce.utils.MacroStringHelper.checkString(MacroStringHelper.java:97)
at hudson.plugins.perforce.utils.MacroStringHelper.substituteParameters(MacroStringHelper.java:64)
at hudson.plugins.perforce.PerforceSCM.getDepot(PerforceSCM.java:463)
at hudson.plugins.perforce.PerforceMailResolver.findPerforceMailAddressFor(PerforceMailResolver.java:78)
at hudson.plugins.perforce.PerforceMailResolver.findMailAddressFor(PerforceMailResolver.java:25)
at hudson.tasks.MailAddressResolver.resolve(MailAddressResolver.java:112)
at hudson.tasks.Mailer$UserProperty.getAddress(Mailer.java:547)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
...
that we saw during this period as well
It doesn't seem to be impacted the actual running of the freestyle projects but wanted to check why these are in the log files. | Workflow | Original: JNJira [ 157288 ] | New: JNJira + In-Review [ 179558 ] |
Jenkins IRC Bot
made changes -
| Component/s | New: p4-plugin [ 19224 ] | |
| Component/s | Original: perforce-plugin [ 15506 ] |
Provide details please. Where are you seeing these logs? What sort of job are you using? What OS? Jenkins version? Plugin version?