User forums > General (but related to Code::Blocks)

CodeBlocks being called from hudson (on linux)

<< < (4/10) > >>

killerbot:
I am trying the personality idea.
This is what I did (experiment from a shell)

1) copied my default.conf to another directory and renamed it to hudson_cb.conf
2) in a shell : codeblocks --personality=/home/killerbot/hudson_cb.conf
3) --> was just like a very first run of CB,so also compiler detection
4) closed that CB --> wanted to save a default.conf , clicked OK
5)
--- Code: ---Could not save config file...: Warning
Aborted
--- End code ---
Even when I kept it named as default.conf, same thing.

Jenna:
the conf-file has to be either in the users ~/.codeblocks directory or in the same directory as the C::B executable.
As workaround, you can use a relative path (starting from your exe-folder), in your case -p ../../../home/killerbot/.codeblocks/.default (or wherever the conf-file you want to use is located).
The file-ending is appended automatically by C::B.

Jenna:
The clean solution would be to create a real C::B console-app.

I will try to revive my ugly patch (mentioned before) and instead of using tons of ifdefs, split he used parts of C::B (mainly compiler-plugin, some core-sdk parts like plugin-manager etc.) into a base-part, that works also on a console and a derived (gui-) part.

killerbot:
I made a copy of my default.conf, renamed it to hudson.conf and copied next to my system codeblocks executable.

and then had hudson launch CB with --personality=hudson.

The good news : it ran.

The less good news :
- no stdout output to discover, so one might even wonder if anything did build ...
- not tried yet : but probably on a build error, things will remain invisible, and we would have no clue if it succeeded or what did fail (gonna try this later on)

When I use the above mentioned manual launch of hudson, then we could see the build progress dialog, and next to that hudson saw coming in (through stdout ??) the content of that build progress dialog. That way it can be seen in the hudson build log what has happened, and in case something failed, what had failed.

So to be really useful, I think we need that stdout behavior, How can we get that back, combined with the xinit/xvnc/personality way.

Jenna:
I always write the log to a html-file, that's not the same, but a possible solution.
You can also try to redirect stdout/stderr to a file (and show it with tail -f flename) or a tty to see the output.

Navigation

[0] Message Index

[#] Next page

[*] Previous page