[ 
https://issues.apache.org/jira/browse/TIKA-4609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18048549#comment-18048549
 ] 

ASF GitHub Bot commented on TIKA-4609:
--------------------------------------

nddipiazza opened a new pull request, #2508:
URL: https://github.com/apache/tika/pull/2508

   ## Summary
   Fixes https://issues.apache.org/jira/browse/TIKA-4609
   
   Reduces Maven verbosity in GitHub Actions workflows to make error messages 
easily visible.
   
   ## Changes Made
   
   Added two Maven flags to all workflow files:
   - `-B` (batch mode) - Suppresses interactive progress output
   - 
`-Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn`
 - Suppresses Maven artifact download/upload progress messages
   
   ## Impact
   
   **Before:** CI logs were flooded with Maven transfer progress making it 
nearly impossible to find error messages
   
   **After:** Clean, concise output with error messages clearly visible
   
   ## Affected Workflows
   
   - `.github/workflows/main-jdk17-build.yml`
   - `.github/workflows/main-jdk21-build.yml`
   - `.github/workflows/main-jdk25-build.yml`
   - `.github/workflows/main-jdk17-windows-build.yml`
   - `.github/workflows/main-jdk17-windows-build-multi-locale.yml`
   
   ## Testing
   
   This change only affects CI output verbosity and does not change build 
behavior.




> Reduce Maven verbosity in GitHub Actions workflows
> --------------------------------------------------
>
>                 Key: TIKA-4609
>                 URL: https://issues.apache.org/jira/browse/TIKA-4609
>             Project: Tika
>          Issue Type: Improvement
>            Reporter: Nicholas DiPiazza
>            Priority: Minor
>
> h2. Problem
> The GitHub Actions workflows are running Maven with extremely verbose output, 
> making it nearly impossible to read error messages in the GitHub Actions UI. 
> The log output is so verbose that users have to download the raw log files to 
> find actual error messages.
> h2. Impact
> * Developers cannot quickly diagnose CI failures
> * CI logs are difficult to navigate and scroll through
> * Error messages are buried in verbose Maven transfer progress output
> * This wastes developer time troubleshooting CI issues
> h2. Solution
> Reduce Maven verbosity in GitHub Actions workflows by:
> # Using {{-B}} (batch mode) to reduce progress output
> # Using 
> {{-Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn}}
>  to suppress download progress
> # Ensuring error messages are easily visible in the CI output
> h2. Affected Files
> * {{.github/workflows/*.yml}} - All workflow files that run Maven commands
> h2. Example
> *Current:* {{mvn clean test install javadoc:aggregate -Pci}}
> *Proposed:* {{mvn clean test install javadoc:aggregate -Pci -B 
> -Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn}}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to