Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Che-Server: Develocity integration #23358

Open
ribafish opened this issue Feb 21, 2025 · 0 comments
Open

Che-Server: Develocity integration #23358

ribafish opened this issue Feb 21, 2025 · 0 comments
Assignees
Labels
kind/enhancement A feature request - must adhere to the feature request template. status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach

Comments

@ribafish
Copy link

ribafish commented Feb 21, 2025

Is your enhancement related to a problem? Please describe

As one of the impactful Eclipse projects, we (the Develocity Solutions team) would like to invite you to be a part of the Eclipse Develocity evaluation initiative.

Describe the solution you'd like

This improvement will enhance the functionality of the Che-Server build by publishing build scans to develocity-staging.eclipse.org, hosted by the Eclipse Foundation and run in partnership between the Eclipse Foundation and Gradle. This Develocity is freely available for use by the Eclipse Che-Server project and all other Eclipse projects.

On this Develocity instance, the Eclipse Che-Server project 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. For example, look at the Quarkus instance trends dashboard with the ci filter applied.
  • Build failure analytics for enhanced investigation and diagnosis of build failures. You can also explore the Quarkus instance for example of a different OSS projects Develocity instance.
  • Test failure analytics to better understand trends and causes around slow, failing, and flaky tests. Going to the Quarkus instance again, this will probably give you a better representation of the type of data available. You can also order it by flakiness, which is a good starting point when deciding which tests need fixing the most.

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

Describe alternatives you've considered

No response

Additional context

Here is a blog post abut Develocity from Eclipse Foundation, as well as a Develocity presentation, made in collaboration with Eclipse Foundation (and Gradle).

More information can be read in the Eclipse announcement.

IMPORTANT: If your project is interested in being a part of this initiative, please reach out to Eclipse infra by filling out a helpdesk ticket to get the CI setup and credentials.

@ribafish ribafish added the kind/enhancement A feature request - must adhere to the feature request template. label Feb 21, 2025
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Feb 21, 2025
@ibuziuk ibuziuk self-assigned this Feb 24, 2025
@ibuziuk ibuziuk added status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Feb 24, 2025
@ibuziuk ibuziuk moved this to 📅 Planned in Eclipse Che Team A Backlog Feb 24, 2025
@ibuziuk ibuziuk moved this from 📅 Planned to Unplanned Tasks in Eclipse Che Team A Backlog Feb 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement A feature request - must adhere to the feature request template. status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach
Projects
Status: Unplanned Tasks
Status: No status
Development

No branches or pull requests

3 participants