Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-61843

Timestamp missing for trailing lines in view as plain text mode.

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major Major
    • timestamper-plugin
    • Widows 10
      Jenkins 2.222.1
      Timestamper 1.11.2
    • 1.11.3

      I upgrade Jenkins and it's plugins once a month, and 2 days ago, 04/06/2020 was that day.

      After upgrading plugins and Jenkins I noticed that the timestamper output isn't always working.

      The web 'console' view works. It shows timestamps all the way to the last line, for example:

      2020-04-08 07:25:53 
      2020-04-08 07:25:53 TestCommon_32R.exe ....
      2020-04-08 07:25:53 Build was aborted
      2020-04-08 07:25:53 Archiving artifacts
      2020-04-08 07:25:53 Triggering a new build of GetLogFile-Trigger
      2020-04-08 07:25:53 Finished: FAILURE
      

      However if I select the "View as plain text" link the timestamps stop part way through the output, and the timestamps don't match the web 'console' output. This is illustrated below:

      2020-04-08 07:25:53  [2020-04-08_14-12-41.142000]:BBBB_MSG:INFO Id=LowRiskCCC msg="Device Registration Received from Airport Network" DEVICE=6CBE031B.140A.4901.911B.CF997C5CCCDB TOKEN=6D1DF198.8E10.474E.AE32.9FBBE10CAE2E
      2020-04-08 07:25:53  [2020-04-08_14-12-41.157000]:BBBB_MSG:INFO DDDDDDDD=PM_UnitTestFFF Location=###.###.###.###:#### msg=Received Message=EEE_ANNOUNCE_CAPABILITIES, Device=[1,6CBE031B.140A.4901.911B.CF997C5CCCDB]
      2020-04-08 07:25:53  [2020-04-08_14-12-41.157000]:BBBB_MSG:INFO DDDDDDDD=PM_UnitTestFFF Location=###.###.###.###:#### msg=FFF_REC_MSG Device=[1,6CBE031B.140A.4901.911B.CF997C5CCCDB] Type=[EEE_ANNOUNCE_CAPABILITIES,10004] RemoteHost=###.###.###.###:#### CurState=1
        [2020-04-08_14-12-41.157000]:BBBB_MSG:INFO DDDDDDDD=PM_UnitTestFFF Location=###.###.###.###:#### msg=Sent Message=EEE_CAPABILITIES_RESPONSE, Device=[1,6CBE031B.140A.4901.911B.CF997C5CCCDB]
        [2020-04-08_14-12-41.188000]:BBBB_MSG:INFO DDDDDDDD=PM_UnitTestFFF Location=###.###.###.###:#### msg=Received Message=EEE_CONFIGURATION_REQUEST, Device=[1,6CBE031B.140A.4901.911B.CF997C5CCCDB]
        [2020-04-08_14-12-41.188000]:BBBB_MSG:INFO DDDDDDDD=PM_UnitTestFFF Location=###.###.###.###:#### msg=FFF_REC_MSG Device=[LowRiskCCC,1,6CBE031B.140A.4901.911B.CF997C5CCCDB] Type=[EEE_CONFIGURATION_REQUEST,20000] RemoteHost=###.###.###.###:#### CurState=2
        [2020-04-08_14-12-41.188000]:BBBB_MSG:INFO DDDDDDDD=PM_UnitTestFFF Location=###.###.###.###:#### msg=Sent Message=EEE_CONFIGURE_DEVICE_REQUEST, Device=[1,6CBE031B.140A.4901.911B.CF997C5CCCDB]
      

      The output bove shows the line

      2020-04-08 07:25:53  [2020-04-08_14-12-41.142000]:BBBB_MSG:INFO Id=LowRiskCCC msg="Device Registration Received from Airport Network" DEVICE=6CBE031B.140A.4901.911B.CF997C5CCCDB TOKEN=6D1DF198.8E10.474E.AE32.9FBBE10CAE2E
      

      at 2020-04-08 07:25:53. However, the 'web console' output shows that with a timestamp of 2020-04-08 07:12:41

      I'm not sure if this makes a difference but the log output is very large. The web 'console' view indicates that it is 1,013KB

      The timestamping in the 'plain text' view stopped at line 8673 of the output, approximately 1,281,994 charters into the output. 716 lines of the plain text output does not have a timestamp.

            basil Basil Crow
            rocha_stratovan John Rocha
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: