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

Build marked as failure because of crashing checkstyle

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Critical
    • Resolution: Duplicate
    • Component/s: checkstyle-plugin
    • Labels:
      None
    • Environment:
      Windows Server 2008 R2 Standard Service Pack 1 (latest updates from Windows updates installed),
      Oracle Java 1.8.0_66-b18,
      Jenkins 2.55 (weekly release),
      Checkstyle Plugin 3.48
    • Similar Issues:

      Description

      We have updated from Jenkins 2.51 to 2.55 and also updated all installed plugins to the latest versions (Checkstyle plugin to 3.48) and after the update we can't build anymore our project. The compilation itself is working, but collecting the checkstyle warning leads to the following error:

      [CHECKSTYLE] Computing warning deltas based on reference build #4350
       ERROR: Build step failed with exception
       java.nio.file.InvalidPathException: Illegal char <:> at index 87: D:\Jenkins\jobs\CoreService\workspace\svn\source\de\v5\coreservice\file:\D:\Jenkins\jobs\CoreService\workspace\svn\source\de\v5\coreservice\server\request\lpr\AddSyncIDHelperFactory.java

       

      After that the build is marked as failure because of the failing checkstyle run. Before the update everything runs fine and there were no configuration or project settings changes from us before and after the Jenkins update.

        Attachments

          Issue Links

            Activity

            Hide
            drulli Ulli Hafner added a comment - - edited

            The reason is a core update.

            Can you please check what happened before the core update? Has the warning line (that caused the exception) a correct file name? In your log there is the strange filename

            D:\Jenkins\jobs\CoreService\workspace\svn\source\de\v5\coreservice\file:\D:\Jenkins\jobs\CoreService\workspace\svn\source\de\v5\coreservice\server\request\lpr\AddSyncIDHelperFactory.java.
            
            Show
            drulli Ulli Hafner added a comment - - edited The reason is a core update. Can you please check what happened before the core update? Has the warning line (that caused the exception) a correct file name? In your log there is the strange filename D:\Jenkins\jobs\CoreService\workspace\svn\source\de\v5\coreservice\file:\D:\Jenkins\jobs\CoreService\workspace\svn\source\de\v5\coreservice\server\request\lpr\AddSyncIDHelperFactory.java.
            Hide
            daniel_isenmann Daniel Isenmann added a comment -

            Before the update the checkstyle log looked like this:

             

            [WARNINGS] Plug-in Result: Success - no threshold has been exceeded
            [CHECKSTYLE] Collecting checkstyle analysis files...
            [CHECKSTYLE] Finding all files that match the pattern svn/source/de/v5/coreservice/checkstyle_errors.xml
            [CHECKSTYLE] Parsing 1 file in D:\Jenkins\jobs\CoreService\workspace
            [CHECKSTYLE] Successfully parsed file D:\Jenkins\jobs\CoreService\workspace\svn\source\de\v5\coreservice\checkstyle_errors.xml with 9519 unique warnings and 0 duplicates.
            [CHECKSTYLE] Computing warning deltas based on reference build #4349
            [FINDBUGS] Collecting findbugs analysis files...
            

            The "strange" filename is inside the checkstyle_errors.xml and it's looking exactly like the one in the error message. I don't know how it looked before because I can't revert the Jenkins core update, it's our productive server and I can't risk a longer downtime.

             

             

            Show
            daniel_isenmann Daniel Isenmann added a comment - Before the update the checkstyle log looked like this:   [WARNINGS] Plug-in Result: Success - no threshold has been exceeded [CHECKSTYLE] Collecting checkstyle analysis files... [CHECKSTYLE] Finding all files that match the pattern svn/source/de/v5/coreservice/checkstyle_errors.xml [CHECKSTYLE] Parsing 1 file in D:\Jenkins\jobs\CoreService\workspace [CHECKSTYLE] Successfully parsed file D:\Jenkins\jobs\CoreService\workspace\svn\source\de\v5\coreservice\checkstyle_errors.xml with 9519 unique warnings and 0 duplicates. [CHECKSTYLE] Computing warning deltas based on reference build #4349 [FINDBUGS] Collecting findbugs analysis files... The "strange" filename is inside the checkstyle_errors.xml and it's looking exactly like the one in the error message. I don't know how it looked before because I can't revert the Jenkins core update, it's our productive server and I can't risk a longer downtime.    

              People

              • Assignee:
                drulli Ulli Hafner
                Reporter:
                daniel_isenmann Daniel Isenmann
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: