• Type: Bug
• Resolution: Fixed
• Priority: Major
• Component/s: cppcheck-plugin
• Labels:

  None
• Environment:

  Jenkins Version: 2.12
  Cppcheck Plug-in 1.21

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

Josias Inacio da Silva Filho created issue - 2017-03-13 20:28

Josias Inacio da Silva Filho made changes - 2017-03-13 20:29

Link

New: This issue is related to JENKINS-9913 [ JENKINS-9913 ]

Josias Inacio da Silva Filho made changes - 2017-03-13 20:29

Link

New: This issue is related to JENKINS-10234 [ JENKINS-10234 ]

Josias Inacio da Silva Filho made changes - 2017-03-13 20:30

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 - 2017-03-13 20:30

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 - 2017-03-13 20:31

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 - 2017-03-14 20:38

Status

Original: Open [ 1 ]

New: In Progress [ 3 ]

Marco Steffan made changes - 2018-07-11 06:52

Resolution		New: Fixed [ 1 ]
Status	Original: In Progress [ 3 ]	New: Resolved [ 5 ]