Hide useless debug output from werft job

[sagor999]

Bug description

Here is an example, I have a failed job and have to scroll through hundreds of lines of debug output (get go package output) to get to the bottom of it and actually see an error message:

Werft: https://werft.gitpod-dev.com/job/gitpod-build-jenting-13980.11

Can we hide that debug output?

Steps to reproduce

n\a

Workspace affected

No response

Expected behavior

No response

Example repository

No response

Anything else?

No response

[meysholdt]

Is this issue about completely removing the logs, or is it about hiding them in CI by default while still having a way to access them?
I assume the latter because I assume the logs are useful to see if the build is doing something (downloading stuff) and to see the exact versions that got pulled into the build.

If it's about hiding the logs, we should fix https://github.com/gitpod-io/ops/issues/5749 first and then look into it.

If this is urgent and about removing the logs completely, I think we'll need to adopt https://github.com/gitpod-io/leeway to make this happen. In this case, can you file an issue in the leeway repository?

Let me know if I'm missing something.

[sagor999]

Removing them from CI by default would be a great start.
But I would imagine either way it would require some sort of leeway modification to enable that, so created issue gitpod-io/leeway#107

[mads-hartmann]

The Leeway issue has been fixed, keeping this open version 0.6.0 is in use in our dev image.

[sagor999]

This has been fixed already. Closing.