Skip to content

#1116 Integrate Develocity into Maven build

This PR will enable you to publish Build Scans to develocity-staging.eclipse.org as requested here.

This PR publishes a build scan for every CI build and for every local build from an authenticated Eclipse committer. The build will not fail if publishing fails. Local and remote caching was left disabled on this PR by design so that the build is not affected by this change.

The build scans of the Eclipse ESCET project are published to the Develocity instance at develocity-staging.eclipse.org, hosted by the Eclipse Foundation and run in partnership between the Eclipse and Gradle. This Develocity instance has all features and extensions enabled and is freely available for use by the Eclipse ESCET project and all other Eclipse projects.

On this Develocity instance, Eclipse ESCET will have access not only to all of the published build scans but also to 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

This will also enable you to (optionally) use build time optimization features, such as (remote) build caching and Predictive Test Selection.

More information can be read in the Eclipse announcement. This is the first part of Develocity integration discussed in issue no. #1116 (closed). The second part, if you opt for it, would be to enable caching for the project.

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

Addresses #1116 (closed)

Edited by Dennis Hendriks

Merge request reports

Loading