Make shhh.py not the default

Bug #408564 reported by Max Bowsher
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

I realize that there is a level of personal preference involved, but after seeing some similar sentiment on #launchpad-dev, I'm filing this bug anyway.

I think the use of shhh.py in Launchpad's buildsystem should not be on by default. The buildsystem output, presented live as it happens is a useful indication of progress. Knowledge of what the build output looks like when the build is working correctly is useful when the build does break. The Launchpad buildsystem is not so extremely verbose simply displaying all the build output is a problem.

I would prefer that shhh.py not be used by default. If that isn't going to happen, I'd be interested in the rationale for having shhh.py on by default, and would like to propose to make it configurable via a ~/.rocketfuel.makevars file.

affects: launchpad → launchpad-foundations
Revision history for this message
Stuart Bishop (stub) wrote :

Quiet should be the default so the output of the automated deployments like edge and staging is readable.

'make SHHH="" ' disables this behavior. It would be great if the default behavior was configurable by a developer, eg. in the existing ~/.rocketfuel-env.sh.

Changed in launchpad-foundations:
status: New → Triaged
Revision history for this message
Max Bowsher (maxb) wrote :

I don't think automated deployments are relevant in setting default behaviour. By definition, they're automated, so their automation can automatically invoke things with a parameter selecting quieter behaviour than the default if so desired.

Curtis Hovey (sinzui)
Changed in launchpad-foundations:
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.