Jenkins and Jenkins-slave charms
Mark Shuttleworth
mark at ubuntu.com
Thu Jan 9 15:30:21 UTC 2014
On 09/01/14 14:36, Steve Powell wrote:
> 1) the `debug-log` command is not documented very well: executing it
> without parameters tails the log (forever) until ^C’d out. To see the
> whole of the log so far execute "juju debug-log -n 1”, and then ^C
> out. (“-n 0” is invalid for some reason);
Nick, could you review the docs for this piece and make sure they
reflect current reality? And perhaps a juju-core person can comment on
the -n 0 situation.
> 2) there is a lot of pinging going on in the log, which you have to
> ignore, basically; it is hard to tell when everything quiesces, and it
> appears that it is important to know!
Perhaps we can make that ping logging a -vv option, and be explicit
about quiescence in a -v?
>
> Anyhow, I’m now running a jenkins server and two connected slaves with
> customised tools setup in the cloud without having to touch these
> machines or the cloud services (after getting the keys). I’m quite happy!
Glad to hear it, thanks for the running debugging :). I understand
debug-hooks have made a lot of progress in the past month or two, not
sure what's landed where.
Mark
More information about the Juju
mailing list