remove --verbose flag from scratch fbc building task#884
Merged
Conversation
Signed-off-by: Adam D. Cornett <adc@redhat.com>
Allda
approved these changes
Jan 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Merge Request Checklists
Motivation
This
--verboseflag seems to just be left over developer logic. This extra flag doesn't seem to yield any value for partners or support, since it's just logging encoded json of the FBC yaml. The issue with this logging is that it blocks partners that have operators with multiple CRD's/resources in their bundle from being able to update their logs to our pipeline. This in tern means there is a failure/error in their CI that calls this CI pipeline.We still get the necessary info to support failures in this task without this flag, see the below log output