[ 
https://issues.apache.org/jira/browse/GEODE-10492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jinwoo Hwang updated GEODE-10492:
---------------------------------
    Description: 
When Apache RAT audit fails during CI builds, developers currently have no 
visibility into which specific files are flagging as having unapproved 
licenses. The RAT plugin generates a detailed HTML report but this report is 
only available on the CI runner and is lost when the build completes.
h2. Problem
 * RAT failures show generic error: "Apache Rat audit failure - 2 unapproved 
licenses"
 * No way to identify which specific files are causing the failure
 * Developers must guess at problematic files or make speculative exclusions
 * Debugging requires multiple CI runs and trial-and-error approaches

h2. Benefits
 * Developers can download and examine the actual RAT report
 * Precise identification of files missing license headers
 * Faster resolution of license compliance issues
 * Reduced CI resource usage from fewer debugging runs
 * Better visibility into license audit process

h2. Implementation Details
 * Artifact only uploaded on build failure to avoid unnecessary storage
 * Report available for download from GitHub Actions run summary
 * Compatible with existing RAT plugin configuration
 * No impact on successful builds

h2. Testing
 * Artifact uploads when RAT task fails
 * Downloaded report correctly identifies offending files
 * No artifacts created on successful builds
 * Report format is readable and actionable

  was:
When Apache RAT audit fails during CI builds, developers currently have no 
visibility into which specific files are flagging as having unapproved 
licenses. The RAT plugin generates a detailed HTML report 
([index.html|vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/workbench.html])
 but this report is only available on the CI runner and is lost when the build 
completes.
h2. Problem
 * RAT failures show generic error: "Apache Rat audit failure - 2 unapproved 
licenses"
 * No way to identify which specific files are causing the failure
 * Developers must guess at problematic files or make speculative exclusions
 * Debugging requires multiple CI runs and trial-and-error approaches


> Add CI artifact upload for Apache RAT audit reports to aid debugging license 
> compliance failures
> ------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-10492
>                 URL: https://issues.apache.org/jira/browse/GEODE-10492
>             Project: Geode
>          Issue Type: Improvement
>            Reporter: Jinwoo Hwang
>            Assignee: Jinwoo Hwang
>            Priority: Major
>
> When Apache RAT audit fails during CI builds, developers currently have no 
> visibility into which specific files are flagging as having unapproved 
> licenses. The RAT plugin generates a detailed HTML report but this report is 
> only available on the CI runner and is lost when the build completes.
> h2. Problem
>  * RAT failures show generic error: "Apache Rat audit failure - 2 unapproved 
> licenses"
>  * No way to identify which specific files are causing the failure
>  * Developers must guess at problematic files or make speculative exclusions
>  * Debugging requires multiple CI runs and trial-and-error approaches
> h2. Benefits
>  * Developers can download and examine the actual RAT report
>  * Precise identification of files missing license headers
>  * Faster resolution of license compliance issues
>  * Reduced CI resource usage from fewer debugging runs
>  * Better visibility into license audit process
> h2. Implementation Details
>  * Artifact only uploaded on build failure to avoid unnecessary storage
>  * Report available for download from GitHub Actions run summary
>  * Compatible with existing RAT plugin configuration
>  * No impact on successful builds
> h2. Testing
>  * Artifact uploads when RAT task fails
>  * Downloaded report correctly identifies offending files
>  * No artifacts created on successful builds
>  * Report format is readable and actionable



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

Reply via email to