| [cross-project-issues-dev] Develocity - Evaluation Period Extension & Key Insights |
Hi everyone,
Following our recent Develocity webinar on February 6th 2025, we would like to share some key updates with you.
If you missed the session or would like to revisit it, you can find the webinar recording and the related blog post on the Eclipse CBI website and the Eclipse Foundation Youtube channel:
🎥 Webinar recording
📄 Blog post: Eclipse CBI Blog
This webinar was a good occasion to discuss the Develocity platform, and get some first key performance results on involved projects. Gasper Kojek from Gradle gave us an insightful overview on how Develocity works and what could be the benefits for Eclipse projects.
As mentioned during the webinar, we have decided to extend the Develocity evaluation period until the end of June 2025. This extension allows more time to explore its advantages, onboard additional projects, and further optimize build processes.
If you haven’t had the chance to explore Develocity yet, please visit the staging instance: Develocity Staging Instance
This is what Develocity can bring to your project:
Better visibility into build and test performance
Faster build times through dedicated caching
Identification flaky tests
CI resources usage optimization
Visibility into your Gradle, Maven, Bazel and sbt builds, with beta support for npm and Python
While only a few projects have fully enabled remote caching, the initial results are promising. These are some recent benefits on some Eclipse projects:
openvsx-server: 34% CI build time reduction, and up to 86% savings (2m 5s) for test builds
Che server (currently onboarding): initial savings of 52s, with potential improvements up to 5m 40s
buildship (currently onboarding): 25s average improvement, with further optimization opportunities
membership.eclipse.org: 40% build time reduction (1m 56s saved on average)
Beyond improving build times, Develocity also helps identify flaky tests and provides valuable insights to address non-verification failures in CI. For instance, in the Mylyn project, one test was found to be flaky 53% of the time, highlighting Develocity's effectiveness in diagnosing such issues. Develocity can highlight issues like these, which can be highly beneficial, as project and test instability can be a major issue for contributors and project maintainers.
The Gradle team is also actively working on support for Tycho tests and Tycho goal caching, which will further enhance performance, particularly for projects using Tycho like mylyn, escet, …
To help us better understand your needs and improve the evaluation of Develocity, we’d love to hear from you!
Please take a few minutes to complete our survey: Develocity Webinar and Community Feedback
If you have any questions or need assistance integrating Develocity into your projects, feel free to reach out by opening a helpdesk ticket or by starting a conversation on the chat service #eclipsefdn.it:matrix.eclipse.orgEclipse Foundation: The Community for Open Collaboration and Innovation