Details

    • Similar Issues:

      Description

      The CheckStyle Plugin for Jenkins seems to be unreliable.
      Without any modifications in the code, the plugins logs warnings.
      These warnings automatically get fixed in the next build.
      Is there a way out to correct these warnings?

        Attachments

          Activity

          Hide
          drulli Ulli Hafner added a comment -

          Can you add some more details? And which versions are you using? Which build type? Do you mean new warnings?

          Show
          drulli Ulli Hafner added a comment - Can you add some more details? And which versions are you using? Which build type? Do you mean new warnings?
          Hide
          axa_capgemini Capgemini Axa added a comment -

          The build for checkstyle plugin is launched every morning.
          So,for example yesterday morning, there were 15 warnings...(high and low), this morning it showed 35 warnings even though no code had been modified between yesterday and today. The warnings should have been 15 today.
          The version is 3.32 and the one installed is 2.14 in jenkins.
          The checkstyle jar used to generate the results is checkstyle5.0.jar

          Show
          axa_capgemini Capgemini Axa added a comment - The build for checkstyle plugin is launched every morning. So,for example yesterday morning, there were 15 warnings...(high and low), this morning it showed 35 warnings even though no code had been modified between yesterday and today. The warnings should have been 15 today. The version is 3.32 and the one installed is 2.14 in jenkins. The checkstyle jar used to generate the results is checkstyle5.0.jar
          Hide
          drulli Ulli Hafner added a comment -

          Does your checkstyle report contain full paths to the source files?

          Please attach from the first and the second build you mentioned:

          • the console log (only lines with CHECKSTYLE prefix)
          • the checkstyle.xml files produced by my plug-in (in the build folder of your job)

          Is this a maven or freestyle job?

          Show
          drulli Ulli Hafner added a comment - Does your checkstyle report contain full paths to the source files? Please attach from the first and the second build you mentioned: the console log (only lines with CHECKSTYLE prefix) the checkstyle.xml files produced by my plug-in (in the build folder of your job) Is this a maven or freestyle job?
          Hide
          drulli Ulli Hafner added a comment -

          Please reopen if you have more details on this issue.

          Show
          drulli Ulli Hafner added a comment - Please reopen if you have more details on this issue.

            People

            • Assignee:
              drulli Ulli Hafner
              Reporter:
              axa_capgemini Capgemini Axa
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: