Closed nitrocode closed 5 months ago
Is there a specific use case for this? I recall we tried that before and it cluttered the build progress output and also was meaningless as the intent is to always show the build output.
I'm closing this one but feel free to continue the discussion.
I was trying to find other log output and it was an obstacle to scroll above the docker buildx build
.
I figured grouping it would be easy as it's already done in other places. I wonder how the previous implementation cluttered the build progress.
If it was behind a non-default flag, would it be more palatable to add?
Description
It would be nice to group the main build output like the action does in the other groups that precede the
docker buildx build
stephttps://github.com/docker/build-push-action/blob/9f6f8c940b91232557f8699b21341a08624a8dce/src/main.ts#L71-L83
Maybe
To keep existing functionality, it could be behind a flag such as
group_build_output: true
which can default tofalse
.