You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Request: Please add a configurable parameter/switch for enabling/disabling progress bar output for terminal-based BIB runs
Context:
When feature #765 was implemented, it took away the ability to monitor detailed progress of BIB runs that are launched manually. Bootc/image mode is new to most users, and having the ability to watch the progress of manual builds aids with learning and troubleshooting.
My initial feedback and other supporting responses can be found here: #765 (comment)
Please let me know if you need additional info to support the request.
The text was updated successfully, but these errors were encountered:
Hey, thanks for your issue and sorry that this change caused you trouble.
The progress override is already possible (but poorly documented currently) via --progress=plain in #776 we will document this better and also renameto --progress=verbose as this seems to be resonating more with the users. There was also the suggestion have add -v as a shortcut to enabling "verbose" output which I quite like.
Just to double check: in a CI pipeline like github the auto-detection should already switch to the verbose progress automatically, your issue describes running it from the terminal? Or do you also see issues with the auto-detect?
Request: Please add a configurable parameter/switch for enabling/disabling progress bar output for terminal-based BIB runs
Context:
When feature #765 was implemented, it took away the ability to monitor detailed progress of BIB runs that are launched manually. Bootc/image mode is new to most users, and having the ability to watch the progress of manual builds aids with learning and troubleshooting.
My initial feedback and other supporting responses can be found here:
#765 (comment)
Please let me know if you need additional info to support the request.
The text was updated successfully, but these errors were encountered: