tylerbertrand opened a new pull request, #666: URL: https://github.com/apache/ranger/pull/666
## What changes were proposed in this pull request? Hi @NikhilPurbhe, it was nice to meet you at Community over Code yesterday! This PR publishes a Build Scan for every CI build and for every local build from an authenticated Apache committer. The build will not fail if publishing fails. The Build Scans of the Apache ranger project are published to the Develocity instance at [develocity.apache.org](https://develocity.apache.org/), hosted by the Apache Software Foundation and run in partnership between the ASF and Gradle. This Develocity instance has all features and extensions enabled and is freely available for use by the Apache ranger project and all other Apache projects. On this Develocity instance, Apache ranger will have access not only to all of the published Build Scans but other aggregate data features such as: Dashboards to view all historical Build Scans, along with performance trends over time Build failure analytics for enhanced investigation and diagnosis of build failures Test failure analytics to better understand trends and causes around slow, failing, and flaky tests Please let me know if there are any questions about the value of Develocity or the changes in this pull request and I’d be happy to address them. ## How was this patch tested? Ran `mvn clean compile` locally after applying the Develocity Maven Extension. The resulting Build Scan for this build can be found [here](https://ge.solutions-team.gradle.com/s/pkc7isrrk42bq). -- 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]
