clayburn opened a new pull request, #2559:
URL: https://github.com/apache/polaris/pull/2559
<!--
Possible security vulnerabilities: STOP here and contact
[email protected] instead!
Please update the title of the PR with a meaningful message - do not
leave it "empty" or "generated"
Please update this summary field:
The summary should cover these topics, if applicable:
* the motivation for the change
* a description of the status quo, for example the current behavior
* the desired behavior
* etc
PR checklist:
- Do a self-review of your code before opening a pull request
- Make sure that there's good test coverage for the changes included in
this PR
- Run tests locally before pushing a PR (./gradlew check)
- Code should have comments where applicable. Particularly
hard-to-understand
areas deserve good in-line documentation.
- Include changes and enhancements to the documentation (in
site/content/in-dev/unreleased)
- For Work In Progress Pull Requests, please use the Draft PR feature.
Make sure to add the information BELOW this comment.
Everything in this comment will NOT be added to the PR description.
-->
@flyrain - this is the PR we discussed today at Community over Code.
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 Polaris project are published to the
Develocity instance at 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 Polaris project and all other Apache projects.
On this Develocity instance, Apache Polaris 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.
--
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]
