mika-collins opened a new pull request, #15486:
URL: https://github.com/apache/grails-core/pull/15486

   ## Description
   
   This PR addresses issue #15088. 
   
   The goal is to consolidate Checkstyle and Codenarc error reports into a 
single known location and publishes them directly to the GitHub Actions job 
summary, making it easier to identify failures without searching through 
multiple zip artifacts. 
   
   ## Changes:
   
   ### `GrailsCodeStyleExtension.groovy`
   - Added `reportsDirectory` property that defaults to 
`rootProject.buildDir/reports/codestyle`, providing a single location for all 
code style reports across subprojects. 
   
   ### `GrailsCodeStylePlugin.groovy`
   - Configured Checkstyle tasks to redirect XML report output to 
`reportsDirectory/checkstyle/<projectname>.xml`.
   - Configured Codenarc tasks to enable XML report output and redirect to 
`reportsDirectory/codenarc/<projectname>.xml`.
   - Each project writes to a file named after the project to avoid 
overwriting. 
   
   ### `.github/workflows/codestyle.yml`
   - Updated artifact upload paths to point to the new reports directory.
   - Changed upload condition from `failure()` to `always()` so reports are 
available regardless of build outcome, aligning with the existing pattern in 
`rat.yml`. 
   - Added "Publish Code Style Report Summary" step to each job, parsing 
Checkstyle and Codenarc XML reports and writing errors directly to the GitHub 
Actions job summary, similar to how RAT errors are already handled. 
   
   ## Testing
   - Verified single report output locally by introducing intentional 
Checkstyle and Codenarc errors and confirming reports are written to 
`build/reports/codestyle`. 
   - End-to-end testing of the job summary output is being verified via this 
draft PR.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to