Perforce builds fail due to special character in the client view
症状
All Perforce builds end with the following error:
java.util.NoSuchElementException
at java.util.StringTokenizer.nextToken(Unknown Source)
at com.tek42.perforce.parse.AbstractPerforceTemplate.parseList(AbstractPerforceTemplate.java:62)
at com.tek42.perforce.parse.Workspaces.getWorkspaceList(Workspaces.java:39)原因
Issue was due to a carraige character in the client view. As a result, Bamboo was unable to parse the output of p4 clients command. For example:
Client sr:VISTA-SANDEEP:LabOperations:rc_2.0.0 2011/04/19 root C:R&DPerforcep4dev.symyx.com_1666sr_SandeepLOI
elease
c_2.0.0 'Autogenerated clientspec. '
Client sr:VISTA-SANDEEP:NotebookStoryTests:rc_6.6.0 2010/10/07 root C:ProjectNotebook 'Autogenerated clientspec. '
Client sr_Sandeep 2011/02/21 root C:/R&D/Perforce/p4dev.symyx.com_1666/sr_Sandeep 'Created by sr. 'ソリューション
We've made the parsing to be more defensive against special characters, but if you do encounter this error we recommend changing the client view to omit the carriage return character.
最終更新日 2013 年 6 月 27 日
Powered by Confluence and Scroll Viewport.