adityamparikh opened a new pull request, #258: URL: https://github.com/apache/solr-mcp/pull/258
Closes #257 Publishes a Gradle build scan of every CI run to the ASF's Develocity instance at [develocity.apache.org](https://develocity.apache.org). A scan records task timings, the full test report, failures, dependency resolution and the build environment. The test history aggregates results across runs, so flaky Testcontainers and compatibility-matrix tests show up as a pattern rather than a one-off red build. ### Changes - **`settings.gradle.kts`** applies `com.gradle.develocity` 4.6.0 and `com.gradle.common-custom-user-data-gradle-plugin` 2.8.0. The configuration follows apache/solr's [`gradle/develocity.gradle`](https://github.com/apache/solr/blob/main/gradle/develocity.gradle): - `server = "https://develocity.apache.org"`, `projectId = "solr-mcp"` - `publishing.onlyIf { (isCiBuild || -Pscan) && it.isAuthenticated }`. Fork PRs receive no secrets, so their builds run unchanged and publish nothing. Local builds publish only when opted in with `-Pscan` and holding an access key. - IP addresses obfuscated; scans tagged with the JDK major version, `PR` and the workflow name. - No remote build cache. That needs a separate write-scoped key from Infra (see #257). - **`ci.yml`, `build-and-publish.yml`, `native.yml`** export `DEVELOCITY_ACCESS_KEY` from `secrets.DEVELOCITY_ACCESS_KEY` at workflow level. A composite action can't read secrets, so this can't live in `.github/actions/setup-java`. These jobs use only GitHub-owned actions besides `./gradlew`. - **`dev-docs/DEVELOPMENT.md`** gets a *Build Scans* section linking the [scan list](https://develocity.apache.org/scans?search.rootProjectNames=solr-mcp) and [90-day test history](https://develocity.apache.org/scans/tests?search.relativeStartTime=P90D&search.rootProjectNames=solr-mcp). ### Access key `DEVELOCITY_ACCESS_KEY` is the secret name most ASF repos use (Kafka, Pulsar, JMeter, Calcite, Samza). apache/solr instead uses a project-scoped `SOLR_DEVELOCITY_ACCESS_KEY`. If Infra provisions that one for this repo, only the three `env:` lines change. Until a key is available, CI behaves exactly as today. ### Verification - `./gradlew build`: successful, 465 tests, 0 failures, 0 skipped. - `CI=true ./gradlew help` and `./gradlew help -Pscan` without a key: successful, no publish attempt. 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
