Current behaviour
$ toolforge build list --debugFails with 'no such option: --debug'.
$ toolforge --debug build listShows debug for te command discovery phase only.
$ toolforge build --debug listWorks!
Ideally all three would be do the same thing, but at least the ones that don't throw an error should be fixed to behave in the same way.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | dcaro | T354714 [harbor,trove] Trove DB filled disk and caused toolforge-build to fail as a result | |||
| Open | BUG REPORT | None | T354726 [builds-cli] --debug option behaviour is confusing |
I think this might be a regression, we should be using environment variables from the main toolforge cli to pass down the debug flags too, though toolforge build --debug and toolforge --debug list can be interpreted as different (debugging different levels of the cli, one starting at the top, the other at the list subcommand).