@BlueHazzard: Yes, still here. Thank's for opening a ticket. The patch from @oBFusCATed did not solve the stall problem for me, but your patch posted before that did (test_FixCompilingIdleHanging_use_PipedProcessLaunch_1.patch). I've running a patched version of CodeBlocks for a few months now on my server.
About my Jenkins setup: I run codeblocks from within a Jenkins pipeline through a batch file.
The pipeline looks something like this:
...
stage('Build'){
steps {
bat "run_codeblocks.bat my_cb_workspace.workspace --build --target=release"
}
}
...
and the batch file 'run_codeblocks.bat' runs CodeBlocks like this:
...
codeblocks.exe" --no-check-associations --no-dde --no-splash-screen %*
...
One could probably just run CodeBlocks directly from the 'bat'-step in the pipeline. However, we do some extra steps in the batch file to work-around some Visual Studio specific issues (like mspdbsrv.exe being killed by Jenkins when building debug targets).