Optionally print stdout of pbuilder to the terminal

[rmohr]

Pbuilder is extremely verbose. This is the reason why stdout is not logged when initially creating the chroot environments. While this is fine when you have a correctly set up environment, it can be quite cumbersome to find out why the creation of a chroot environment failed.

[konsumate]

@rmohr Can you hint into a direction what attribute fields in what files would be necessary to get this "verbose" field as an additional configuration option to show up under the chroot configuration? Is the jenkins generating the configuration fields from the classes dynamically?

[thellef]

@rmohr seems to be a bit unresponsive at the moment; I'll see if I can point you in the right direction.
The UI for the installation is in the src/main/resources/org/jenkinsci/plugins/chroot/tools/ChrootToolsetProperty directory, specifically the config.jelly file. There's also some help files there. I don't know where internationalization is handled.
There's definitely something going on between that and the src/main/java/org/jenkinsci/plugins/chroot/tools/ChrootToolsetProperty.java file - there's a DataBoundConstructor and some accessors with the same names as defined in config.jelly.
The properties are then used by the .../extensions/PBuilderWorker.java class. That's where you might direct stdout to the logger as well (see around lines 89-90; there's a comment about the verbosity).
Happy hacking :-)

[konsumate]

@KodeKarl Implemented it, works - need a bit of time to sanitize the patch. Also I've included some validation checks and more logging to the plugin itself, BUT one thing disturbs me: the listener has only INFO or logfatalerror as logging methods - why is there no debug/trace whatsoever?

[thellef]

Great. Looking forward to it.
What Listener do you mean? Some places we have a BuildListener, other places a TaskListener. I can't find any logging methods in them (see http://javadoc.jenkins-ci.org/), but we can call getLogger() and get something onto which we can print whatever we like. No loglevel support, though, as far as I can see. It just goes into the build's console output.
Some plug-ins use a regular log4j logger, I believe. But that output is only visible via the administration interface (which may or may not be what you're looking for).