A little recap :
CB is a strong IDE, but it is also a strong build tool (focusing now on command line usage) :
- feed it a workspace, and it can build all projects
- feed it a project, and it can build *all* targets [ONLY if there is a virtual target bundling all the targets] [IDEA : I think when no target is specified all targets should be build] Any comments
?
- It can run post build things, either by ,anual commands or by launching several plug-ins (for example run a CppCheck)
As such it can be a good replacement for make files, especially towards continuous integration. Where continuous integration would be configured by a shell script to launch the correct makefiles, it now could be configured to call CB.
I have done long time ago such things on windows, where the CI hudson was calling a 'driver program' which in turn called CB (that driver program created for example the correct config spec for clearcase depending on certain criteria), but forget about windows, time to focus on linux.
There are 2 ways of running hudson :
1) under your regular user account during your regular sessions, you fire up a shell and start the hudson.war manually [java -jar hudson.war]. Hudson will store all it stuff in '.hudson' directory in your home directory
GOOD :
- no issues as described above in the previous replies, there's an xserver, the build window is even visible
BAD :
- it is not automatically started, after each login you need to open up your shell and reissue the command to fire up the hudson.war
Question : I guess this can be automated (how exactly ?)
2) install a package for your distribution, this will also activate a startup script (for me : OpenSuse ->/etc/init.d/hudson, with a config file /etc/sysconfig/hudson), the hudson stuff now ends up somewhere under /var/lib/hudson and /varr/log/hudson) and it is being launched by the startup script as the user 'hudson' which is a member of the group 'hudson'
GOOD :
- automatically launched
- dedicated user for this
- no need to log in with a certain user account
- really a server/service
BAD :
- those gtk issues / xserver issues pop up as described in the previous replies :-(
I tried in the configuration to say the hudson daemon should be run by my account (HUDSON_USER="killerbot") but that didn't help, the issues remain.
So the closet was thet xinit/Xvnc thing but that also fails now due to the compiler detected dialog box invisibly waiting to be clicked ...