Add a log level option in <steep>

[Miniwark]

There are steeps who are build preparations only, like subsertion checkout. Some other who give a lot of informational logs not realy useful like package installs during distutils builds.

Basicaly when i make a build i whoud like to see only Errors and maybe Warnings. Sometimes i even would like to have no logs at all for some steeps.

I would realy apreciate a loglevel option in steeps to avoid unecessary logs in the build display in Trac..

For exemple :

<step id="svn" Description="chechout" loglevel="Error">

Witch will display an record only checkout errors and not all the sometime very long svn logs.

Or :

<step id="svn" Description="chechout" loglevel="Nothing">

Witch will completly disable logs for this steep because i feel it not relevant.

Or :

<step id="egg" Description="Egg build" loglevel="Warning">

Witch will display only the warnings and errors, and not the infos messages.

If the loglevel option is not given, logs will be like now with all logs info + warnig + errors

It's différent from ticket #267 which interfere only at the display logs time. Instead this new feature will also allow to avoid to fill the database with unecessary logs and record only the interesting one in the developer point of view.

[Miniwark]

I see just now then there is "verbose" option for svn, this is partialy what i seek, but i woul have been hapy to have the same option for distutils commands.

[osimons]

Problem is that Bitten can't make any general assumption about content and loglevels from command output. Commands (whatever they may be) are executed and produce output according to arguments you pass in, and stdout and stderr will both be interleved in the same text log.

The only adjustment I can imagine being useful (and possible) is having logging="off" so that all command output is dropped and the only stored output from a step is just "Step completed successfully." or "Step completed with errors." (depending on return codes from commands in step).

[osimons]

Actually, that is not quite true - at some stage deep down in the CommandLine class we do have separate stdout and stderr information.

That makes "all", "errors", "output" and "none" possible, I suppose.

[Miniwark]

Apparently an implementation for svn:checkout have been done in r547 (see #284)

As this was my main need, i will be enough happy with this.

Anyway it can be a starting base for a full implementation of the feature.