Gradle Enterprise build scans is now in use for branches in apache/pulsar . For example, the build scan for master branch can be accessed for the 60+ maven build runs from the GitHub Actions workflow run build summary view. master branch build listing: https://github.com/apache/pulsar/actions/workflows/pulsar-ci.yaml?query=branch%3Amaster Example workflow run (contains links to Gradle Enterprise build scans): https://github.com/apache/pulsar/actions/runs/3902082126
-Lari On 2023/01/04 18:16:41 Lari Hotari wrote: > Here's an example of builds scans for all Maven builds that are run as part > of Pulsar CI workflow: > https://ge.apache.org/scans?search.names=Git%20commit%20id%20short&search.timeZoneId=Europe/Helsinki&search.values=db7ab997&selection.buildScanB=ohtx53k6ymsgc > There are 69 maven builds that are run in total in a single execution of > Pulsar CI workflow! > > The build scans are also linked from the GitHub Actions results page, for > example > https://github.com/apache/pulsar/actions/runs/3839199234#summary-10438505199 > shows this. It's easier to navigate to the builds this way. > > I created a PR https://github.com/apache/pulsar/pull/19133 for making the > changes. Please review! > > -Lari > > On 2023/01/04 11:52:14 Lari Hotari wrote: > > Hi all, > > > > ASF Infra team together with Gradle Inc. has setup a dedicated Gradle > > Enterprise instance for Apache projects at https://ge.apache.org/ . > > > > Gradle Enterprise works for both Gradle builds and Maven builds. > > There's a Maven extension which provides the integration for Maven builds, > > https://docs.gradle.com/enterprise/maven-extension/ . > > You can find more information about the benefits of Gradle Enterprise on > > gradle.com . This is also for Maven builds! > > > > The main features are the "build scan insights" and "build cache > > acceleration". At this time, I'm first looking at experimenting with "build > > scan insights" feature. > > > > Apache Beam project seems to be also looking into this: > > https://lists.apache.org/thread/v43djv8f941x2h1r3mptvt92ynplm7mk > > > > I had a chat on ASF slack with Gavin McDonald about this, and Gavin asked > > me to create an infra ticket. I created > > https://issues.apache.org/jira/browse/INFRA-24052 for configuring the > > secret token required for accessing Gradle Enterprise from CI builds. It > > turns out that all Apache projects should already have the token in > > GE_ACCESS_TOKEN environment variable. I'll experiment with that soon. The > > token won't be available for pull request builds. While experimenting, I'll > > create an experimental branch in apache/pulsar so that the builds for this > > branch have access to the required Gradle Enterprise token. > > > > After this experimentation is completed successfully, I'll create a PR for > > enabling Gradle Enterprise builds scans that run scheduled once a day on > > the master branch (scheduled at > > https://github.com/apache/pulsar/blob/9ec1d071c7188a2db694e9d7b359faaf33cb076e/.github/workflows/pulsar-ci.yaml#L25-L26). > > > > BR, > > > > Lari > > >
