[CALCITE-5721] Capture build scans on ge.apache.org to benefit from deep build insights

[clayburn]

This PR publishes a build scan for every CI build on Jenkins and 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 Calcite project are published to the Gradle Enterprise instance at 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 Calcite project and all other Apache projects.

Currently, the Apache Calcite build is configured to publish build scans to the publicly available scans.gradle.com. This pull request enhances that functionality by instead publishing build scans to ge.apache.org. On this Gradle Enterprise instance, Apache Calcite 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

If interested in exploring a fully populated Gradle Enterprise instance, please explore the Maven builds already connected to ge.apache.org, the Spring project’s instance, or any number of other OSS projects for which we sponsor instances of Gradle Enterprise.

Please let me know if there are any questions about the value of Gradle Enterprise or the changes in this pull request and I’d be happy to address them.

[zabetak]

Overall LTGM. Is there a way to test that it works as expected before merging?

[clayburn]

Overall LTGM. Is there a way to test that it works as expected before merging?

Sure, a few things you can do:

• These are the two builds that have run so far for this PR in Jenkins: https://ge.apache.org/scans?search.rootProjectNames=calcite&search.timeZoneId=America/Chicago
• The GitHub Actions workflows aren't able to authenticate since they came from my fork, but you could create a branch in the apache/calcite repo and run the validations against that to see the resulting build scans.
• You could run some local builds by authenticating to https://ge.apache.org with your ASF LDAP credentials, provisioning an access token, and generating scans from local builds.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[zabetak]

I tested the patch by publishing authenticated scans from my local environment and things look good. I left a minor question and will merge this as soon as I get an answer.