[
https://issues.apache.org/jira/browse/SPARK-60212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated SPARK-60212:
-----------------------------------
Labels: pull-request-available (was: )
> Publish Maven and sbt Build Scans to develocity.apache.org
> ----------------------------------------------------------
>
> Key: SPARK-60212
> URL: https://issues.apache.org/jira/browse/SPARK-60212
> Project: Spark
> Issue Type: Improvement
> Components: Build
> Affects Versions: 4.2.0
> Reporter: Jerome Prinet
> Priority: Major
> Labels: pull-request-available
>
> ASF runs a Develocity instance at https://develocity.apache.org that other
> Apache projects use to record CI builds as Build Scans: per-test results with
> history (flaky and slow tests), console logs, failure grouping and build
> performance data.
> This proposes adding the Develocity Maven extension and sbt plugin to Spark's
> builds, so the GitHub Actions builds publish Build Scans there:
> * Build Scans are published only when a _DEVELOCITY_ACCESS_KEY_ secret is
> available, so local builds and contributors' fork CI are unchanged unless
> they opt in with their own key.
> * Maven builds also use the Develocity build cache: CI stores compilation
> outputs in the shared remote cache, and later builds with a key reuse them
> instead of recompiling unchanged modules.
> * Test runs are never cached: Spark tests depend on inputs the cache key
> doesn't track, so Maven's surefire runs are marked not cacheable and sbt runs
> without a build cache. Maven compilation can use the shared remote cache.
> * The key is scoped to the workflow steps that run sbt or Maven.{*}{*}
>
> {*}Prerequisite{*}: an access key for develocity.apache.org from ASF Infra,
> stored as the _DEVELOCITY_ACCESS_KEY_ repository secret. A write access to
> the cache also needs to be requested for CI jobs to push entries to the
> remote cache.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
