• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Blocker Blocker
    • p4-plugin
    • None
    • p4-plugin 1.10.0
      jenkins 2.176.1
      docker lts image ubuntu
      Server version: P4D/LINUX26X86_64/2017.1/1622573 (2018/02/20)

      In upgrading from 1.9.6 to 1.10.1 it seems that the utf8bom filesys options is no longer honoured. Might be related to the p4java upgrade?

      We use this normally on a windows slave to correct old utf8bom issues.

      -Dcom.perforce.p4java.filesys.utf8bom=0

      Attached is a packages.config file synced correctly, and packages.config.borked which is the same file synced with an extra bom character

       

          [JENKINS-58196] UTF8 BOM override issue in 1.10.0

          Karl Wirth added a comment -

          Hi phopkins101. Thanks for reporting this. I think I can reproduce the behavior but wanted to check your configuration. Please answer the following questions:

          • What is the Perforce filetype for 'packages.config' ('p4 filelog packages.config' will give the answer).
          • What Version of P4D and what OS are you using?
          • Is the P4D server running in Unicode mode?
          • How are you setting '-Dcom.perforce.p4java.filesys.utf8bom=0'? For example do you have a command line that starts the slave?
          • What version of Java are you using on the slave?

          Thanks in advance,

          Karl

          Karl Wirth added a comment - Hi phopkins101 . Thanks for reporting this. I think I can reproduce the behavior but wanted to check your configuration. Please answer the following questions: What is the Perforce filetype for 'packages.config' ('p4 filelog packages.config' will give the answer). What Version of P4D and what OS are you using? Is the P4D server running in Unicode mode? How are you setting '-Dcom.perforce.p4java.filesys.utf8bom=0'? For example do you have a command line that starts the slave? What version of Java are you using on the slave? Thanks in advance, Karl

          Peter Hopkins added a comment -

          Thanks for the quick response Karl.

          • (utf8)
          • versions -
            • P4D/LINUX26X86_64/2017.1/1622573 (2018/02/20)
            • CentOS release 6.7
            • Linux 2.6.32-573.12.1.el6.x86_64 #1 SMP Tue Dec 15 21:19:08 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
          • server is not Unicode
          • Using the vSphere slave plugin for jenkins, optional Java startup parameter
          • Slave java = SE RE 1.8.0_152

          Peter Hopkins added a comment - Thanks for the quick response Karl. (utf8) versions - P4D/LINUX26X86_64/2017.1/1622573 (2018/02/20) CentOS release 6.7 Linux 2.6.32-573.12.1.el6.x86_64 #1 SMP Tue Dec 15 21:19:08 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux server is not Unicode Using the vSphere slave plugin for jenkins, optional Java startup parameter Slave java = SE RE 1.8.0_152

          Karl Wirth added a comment -

          P4Java bug - being tracked internally as P4JAVA-1139.

          Karl Wirth added a comment - P4Java bug - being tracked internally as P4JAVA-1139.

          Peter Hopkins added a comment -

          I noticed a few p4java updates in recent plugin release, just wondering if this was addressed?  I don't see this bug in the readme.md though

          Peter Hopkins added a comment - I noticed a few p4java updates in recent plugin release, just wondering if this was addressed?  I don't see this bug in the readme.md though

            p4karl Karl Wirth
            phopkins101 Peter Hopkins
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: