User forums > Help

Codeblocks does not continue build after a command line start.

<< < (2/2)

Henk:
@killerbot
There is a workaround connecting Codeblocks to a display when build from Jenkins. This workaround is in place, so this is (likely) not the cause if this problem. (Would be great to have a headless codeblocks, I could get rid of the workaround).
@oBFusCATed
I am not sure what you meant, is it installing debug symbols for Codeblocks, and then debug Codeblocks?

oBFusCATed:
Yes, this is what I meant

killerbot:
could you tell me your workaround ?

Henk:
Sure, workaround for having a display for Jenkins, is exporting a display before codeblocks is started. This is done with:
#!/bin/sh
export DISPLAY=:2000.0

You will need to have display 2000.
In this case Jenkins runs on a machine without any display.
Before a Jenkins build is started, I login with nomachine. (Otherwise the build will fail)
You will see Codeblocks pop-ups when jenkins starts a build.

Henk:
Just want to report.
The system is running fine now for quite some months.
But using the machine with NoMachine while Codeblocks builds are started through Jenkins, gives this problem.
Since this is a build machine, solution is simple  :)

Navigation

[0] Message Index

[*] Previous page