You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe that one major barrier towards the adaptation of cdash is the overall navigation, ui and ux. I think it is better to adopt the interface of a CI system like TeamCity, or those of tools like sonarcloud and codecov.
More specifically some wishlists:
as a user, I want to (easily) select between different views: projects/explore, overview, builds, commits, pull-requests, settings
as a guest, I want to see what is the status of a project
as a user/developer, I need to navigate builds by the git tree
as a developer, I may need to compare builds
as a guest/user, it is unclear the difference between Nightly, Continuous builds and their relation to the source
as a developer, I would want to submit "private builds" for testing the CI or to analyze test results before submitting a PR.
From there probably exploring the configure/build/test logs, coverage, etc. might be clearer or we can find what other ux improvements can be had there.
The text was updated successfully, but these errors were encountered:
I believe that one major barrier towards the adaptation of cdash is the overall navigation, ui and ux. I think it is better to adopt the interface of a CI system like TeamCity, or those of tools like sonarcloud and codecov.
More specifically some wishlists:
From there probably exploring the configure/build/test logs, coverage, etc. might be clearer or we can find what other ux improvements can be had there.
The text was updated successfully, but these errors were encountered: