borinquenkid commented on code in PR #15530: URL: https://github.com/apache/grails-core/pull/15530#discussion_r3035656639
########## build-logic/plugins/src/main/groovy/org/apache/grails/buildsrc/GrailsTestPlugin.groovy: ########## @@ -0,0 +1,129 @@ +/* + * Licensed to the Apache Software Foundation (ASF) under one + * or more contributor license agreements. See the NOTICE file + * distributed with this work for additional information + * regarding copyright ownership. The ASF licenses this file + * to you under the Apache License, Version 2.0 (the + * "License"); you may not use this file except in compliance + * with the License. You may obtain a copy of the License at + * + * https://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, + * software distributed under the License is distributed on an + * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY + * KIND, either express or implied. See the License for the + * specific language governing permissions and limitations + * under the License. + */ +package org.apache.grails.buildsrc + +import java.time.LocalDateTime +import java.time.format.DateTimeFormatter +import groovy.xml.XmlSlurper +import org.gradle.api.Plugin +import org.gradle.api.Project +import org.gradle.api.tasks.testing.Test +import groovy.transform.CompileDynamic + +class GrailsTestPlugin implements Plugin<Project> { Review Comment: The recent updates to the build logic, particularly the GrailsTestPlugin and GrailsCodeStylePlugin, are designed to shift quality feedback "left"—moving it from the CI environment directly to the developer's local workflow. Developer-Centric Aggregation: Unlike standard build reports that focus on overall success/pass rates, these plugins are failure-focused. They are specifically designed for developers to identify and resolve blockers across a complex multi-module project without sifting through massive logs. Immediate Feedback Loop: With the new aggregateStyleViolations and aggregateTestFailures tasks, developers no longer need to wait for a full CI pipeline execution to see the total impact of their changes. Unified Issue Tracking: The plugins consolidate errors from various tools (CodeNarc, Checkstyle, PMD, SpotBugs, and JUnit) into centralized Markdown reports (TEST_FAILURES.md, CODENARC_VIOLATIONS.md, etc.) at the project root. This provides a single source of truth for all outstanding issues that need addressing before a push. These files are already ignored for check in. Automated Remediation: To further speed up the development cycle, the code style plugin includes a codenarcFix task that automatically repairs common formatting regressions, ensuring the branch remains compliant with project standards with minimal manual effort. -- 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]
