clayburn opened a new pull request, #20187:
URL: https://github.com/apache/pulsar/pull/20187

   ### Motivation
   
   This PR publishes a build scan for every CI build on GitHub Actions and for 
every local build from an authenticated Apache committer. The build will not 
fail if publishing fails.
   
   The build scans of the Apache Pulsar project are published to the Gradle 
Enterprise instance at [ge.apache.org](https://ge.apache.org/), hosted by the 
Apache Software Foundation and run in partnership between the ASF and Gradle. 
This Gradle Enterprise instance has all features and extensions enabled and is 
freely available for use by the Apache Pulsar project and all other Apache 
projects.
   
   Currently, the Apache Pulsar build is configured to publish build scans to 
[ge.apache.org](https://ge.apache.org/) for CI only. This pull request enhances 
that functionality by also publishing build scans to 
[ge.apache.org](https://ge.apache.org/) for authenticated Apache committers. On 
this Gradle Enterprise instance, Apache Pulsar 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
   
   ### Modifications
   
   - Update the Gradle Enterprise Maven Extension to 1.17
   - Remove the logic that copies `ge-extensions.xml` in favor of the more 
conventional `extensions.xml` file. Updates to the `publishIfAuthenticated` 
property in Gradle Enterprise Maven Extension 1.17 will cause the build to 
print no output if the user is not authenticated to 
[ge.apache.org](https://ge.apache.org/).
   
   ### Verifying this change
   
   - [ ] Make sure that the change passes the CI checks.
   
   This change is a trivial rework / code cleanup without any test coverage.
   ### Does this pull request potentially affect one of the following parts:
   
   <!-- DO NOT REMOVE THIS SECTION. CHECK THE PROPER BOX ONLY. -->
   
   *If the box was checked, please highlight the changes*
   
   - [ ] Dependencies (add or upgrade a dependency)
   - [ ] The public API
   - [ ] The schema
   - [ ] The default values of configurations
   - [ ] The threading model
   - [ ] The binary protocol
   - [ ] The REST endpoints
   - [ ] The admin CLI options
   - [ ] The metrics
   - [ ] Anything that affects deployment
   
   ### Documentation
   
   <!-- DO NOT REMOVE THIS SECTION. CHECK THE PROPER BOX ONLY. -->
   
   - [ ] `doc` <!-- Your PR contains doc changes. -->
   - [ ] `doc-required` <!-- Your PR changes impact docs and you will update 
later -->
   - [x] `doc-not-needed` <!-- Your PR changes do not impact docs -->
   - [ ] `doc-complete` <!-- Docs have been already added -->
   
   ### Matching PR in forked repository
   
   PR in forked repository: <!-- ENTER URL HERE -->
   
   <!--
   After opening this PR, the build in apache/pulsar will fail and instructions 
will
   be provided for opening a PR in the PR author's forked repository.
   
   apache/pulsar pull requests should be first tested in your own fork since 
the 
   apache/pulsar CI based on GitHub Actions has constrained resources and quota.
   GitHub Actions provides separate quota for pull requests that are executed 
in 
   a forked repository.
   
   The tests will be run in the forked repository until all PR review comments 
have
   been handled, the tests pass and the PR is approved by a reviewer.
   -->
   


-- 
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: commits-unsubscr...@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to