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

Cppcheck plugin waiting for checkpoint erroneously when concurrent builds are enabled

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • cppcheck-plugin
    • None
    • Jenkins Version: 2.12
      Cppcheck Plug-in 1.21

      Concurrent builds have been recently enabled on my system, and I noticed that Cppcheck plugin is having issues dealing with this new scenario.

      Builds are running in different machines, and are not dependent on each other. However Cppcheck will only continue once they are all completed. This causes a delay of up to a few hours, where the first build will only finish once the last that is currently building has finished as well.

      From the console output:

      Publish Cppcheck results is waiting for a checkpoint on Package Builds ? <job_name> #2229

       

      That seems to be a known bug for plugins written before this Jenkins feature was implemented, some of which had to be modified to address concurrent builds properly.

          [JENKINS-42727] Cppcheck plugin waiting for checkpoint erroneously when concurrent builds are enabled

          Josias Inacio da Silva Filho created issue -
          Josias Inacio da Silva Filho made changes -
          Link New: This issue is related to JENKINS-9913 [ JENKINS-9913 ]
          Josias Inacio da Silva Filho made changes -
          Link New: This issue is related to JENKINS-10234 [ JENKINS-10234 ]
          Josias Inacio da Silva Filho made changes -
          Summary Original: Cppcheck plugin waiting for checkpoint erroneously when concurrent builds is enabled New: Cppcheck plugin waiting for checkpoint erroneously when concurrent builds are enabled
          Josias Inacio da Silva Filho made changes -
          Description Original: Concurrent builds have been recently enabled on my system, and I noticed that Cppcheck plugin is having issues dealing with this new scenario.

          Builds are running in different machines, and are not dependent on each other. However Cppcheck will only continue once they are all completed. This causes a delay of up to a few hours, where the first build will only finish once the last that is currently building has finished as well.

          From the console output:
          Publish Cppcheck results is waiting for a checkpoint on Package Builds ? <job_name> #2229
           

          That seems to be a known bug, and some plugins had to be modified to address concurrent builds properly.           		New: Concurrent builds have been recently enabled on my system, and I noticed that Cppcheck plugin is having issues dealing with this new scenario.

          Builds are running in different machines, and are not dependent on each other. However Cppcheck will only continue once they are all completed. This causes a delay of up to a few hours, where the first build will only finish once the last that is currently building has finished as well.

          From the console output:
          {noformat}
          Publish Cppcheck results is waiting for a checkpoint on Package Builds ? <job_name> #2229{noformat}
           

          That seems to be a known bug, and some plugins had to be modified to address concurrent builds properly.
          Josias Inacio da Silva Filho made changes -
          Description Original: Concurrent builds have been recently enabled on my system, and I noticed that Cppcheck plugin is having issues dealing with this new scenario.

          Builds are running in different machines, and are not dependent on each other. However Cppcheck will only continue once they are all completed. This causes a delay of up to a few hours, where the first build will only finish once the last that is currently building has finished as well.

          From the console output:
          {noformat}
          Publish Cppcheck results is waiting for a checkpoint on Package Builds ? <job_name> #2229{noformat}
           

          That seems to be a known bug, and some plugins had to be modified to address concurrent builds properly.           		New: Concurrent builds have been recently enabled on my system, and I noticed that Cppcheck plugin is having issues dealing with this new scenario.

          Builds are running in different machines, and are not dependent on each other. However Cppcheck will only continue once they are all completed. This causes a delay of up to a few hours, where the first build will only finish once the last that is currently building has finished as well.

          From the console output:
          {noformat}
          Publish Cppcheck results is waiting for a checkpoint on Package Builds ? <job_name> #2229{noformat}
           

          That seems to be a known bug for plugins written before this Jenkins feature was implemented, some of which had to be modified to address concurrent builds properly.
          Marco Steffan made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]

          Marco Steffan added a comment -

          Changes pushed to github. Pull-Request is available

          https://github.com/jenkinsci/cppcheck-plugin/pull/32

          Marco Steffan added a comment - Changes pushed to github. Pull-Request is available https://github.com/jenkinsci/cppcheck-plugin/pull/32

          Josias Inacio da Silva Filho added a comment -

          Thanks Marco.

          Josias Inacio da Silva Filho added a comment - Thanks Marco.

          Matthieu Baerts added a comment -

          Hi Marco,

          Thank you for the fix! Just saw it was finally merged on Github, that's good!

          By chance, do you have any package including your fix? I am not able to build it and it seems ci.jenkins.io is not able to do that as well: https://ci.jenkins.io/job/Plugins/job/cppcheck-plugin/

          Matt

          Matthieu Baerts added a comment - Hi Marco, Thank you for the fix! Just saw it was finally merged on Github, that's good! By chance, do you have any package including your fix? I am not able to build it and it seems ci.jenkins.io is not able to do that as well: https://ci.jenkins.io/job/Plugins/job/cppcheck-plugin/ Matt

            marcosteffan Marco Steffan
            josias Josias Inacio da Silva Filho
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: