For a past few Bob versions, the bob dev/build commands show the output of several Bob internal Git commands during the checkout step on the tty (assuming increased output verbosity).
This may be useful, if the context is clear to the user, i.e., if output verbosity is increased to at least level 2. In this case the output may look like this:
CHECKOUT dev/src/example_repo
+ git remote
origin
+ git ls-remote --get-url origin
https://github.com/example_repo.git
+ git rev-parse --is-shallow-repository
false
+ git rev-parse --verify -q HEAD
[...]
If output verbosity is only set to level 1, the corresponding output looks like this:
CHECKOUT dev/src/example_repo
origin
https://github.com/example_repo.git
false
[...]
This is a bit confusing, since the context of this output is not obvious to the user. It's no output of a user provided checkout script. It's only the output of the checkoutSCM section, whose implementation is not transparent to the user.
It seems that the described behavior has been changed in commit 2c4493a. What was the intention of this commit?
Should this output maybe generated only for an output verbosity level greater than 1?
For a past few Bob versions, the
bob dev/buildcommands show the output of several Bob internal Git commands during the checkout step on the tty (assuming increased output verbosity).This may be useful, if the context is clear to the user, i.e., if output verbosity is increased to at least level 2. In this case the output may look like this:
If output verbosity is only set to level 1, the corresponding output looks like this:
This is a bit confusing, since the context of this output is not obvious to the user. It's no output of a user provided checkout script. It's only the output of the
checkoutSCMsection, whose implementation is not transparent to the user.It seems that the described behavior has been changed in commit 2c4493a. What was the intention of this commit?
Should this output maybe generated only for an output verbosity level greater than 1?