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

Find mechanism to aggregate measure and results #12

Open
romanowski opened this issue Mar 1, 2021 · 0 comments
Open

Find mechanism to aggregate measure and results #12

romanowski opened this issue Mar 1, 2021 · 0 comments
Assignees

Comments

@romanowski
Copy link
Member

Each run of community build will provide a lot of data. We want to find a mechanism to aggregate and store that data.

There is not hard stop how many features we would like to have so I split them into 'must have' and 'nice to have'.

Must have

  • allow to gather and aggregate data on few levels (run of community build, build of a single project and finally run of single target)
  • gather numerical data like no. of warning, errors, failed tests or line compiled. It should also include compilation speed, times, or sizes generated .classes and .jar files
  • allow to report data from distributed build
  • allow to aggregate across different runs (e.g. we want to display time of compilation for given project across many builds)
  • generating reports should be easy
  • easy way to anonymize data

** nice to have **

  • ability to track failures of single test
  • ability to track compilation problems / warning

We would prefer to use some lightweight solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants