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

Add the ability to view some important metrics of assessing how CTSM development is proceeding #2973

Open
ekluzek opened this issue Feb 23, 2025 · 2 comments
Assignees
Labels
bfb bit-for-bit code health improving internal code structure to make easier to maintain (sustainability) enhancement new capability or improved behavior of existing capability
Milestone

Comments

@ekluzek
Copy link
Collaborator

ekluzek commented Feb 23, 2025

It would be helpful to have some ways of viewing development metrics of how things are going. There are limited
charts in insights, and you can only easily do charts with existing project boards.

@ekluzek ekluzek added bfb bit-for-bit enhancement new capability or improved behavior of existing capability FATES A change needed for FATES that doesn't require a FATES API update. testing additions or changes to tests code health improving internal code structure to make easier to maintain (sustainability) and removed FATES A change needed for FATES that doesn't require a FATES API update. testing additions or changes to tests labels Feb 23, 2025
@ekluzek
Copy link
Collaborator Author

ekluzek commented Feb 23, 2025

There's a research group on Software Development called DORA that has a set of metrics to look at:

https://dora.dev/

There's four metrics they recommend

https://dora.dev/guides/dora-metrics-four-keys

The metrics look at development throughput and stability. With two for each, here is a definition of them from the above page:

Throughput
Throughput measures the velocity of changes that are being made. DORA assesses throughput using the following metrics:

Change lead time - This metric measures the time it takes for a code commit or change to be successfully deployed to production. It reflects the efficiency of your delivery pipeline.
Deployment frequency - This metric measures how often application changes are deployed to production. Higher deployment frequency indicates a more efficient and responsive delivery process.
Stability
Stability measures the quality of the changes delivered and the team’s ability to repair failures. DORA assesses stability using the following metrics:

Change fail percentage - This metric measures the percentage of deployments that cause failures in production, requiring hotfixes or rollbacks. A lower change failure rate indicates a more reliable delivery process.
Failed deployment recovery time - This metric measures the time it takes to recover from a failed deployment. A lower recovery time indicates a more resilient and responsive system.

@ekluzek
Copy link
Collaborator Author

ekluzek commented Feb 23, 2025

There is a github action for doing this in github Marketplace:

https://github.com/marketplace/actions/devops-metrics-from-github

@ekluzek ekluzek self-assigned this Mar 4, 2025
@ekluzek ekluzek moved this from Todo to In Progress in LMWG: Sprint Planning Board Mar 4, 2025
@ekluzek ekluzek added this to the ctsm6.1.0 milestone Mar 4, 2025
@ekluzek ekluzek moved this from In Progress to Todo in LMWG: Sprint Planning Board Mar 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bfb bit-for-bit code health improving internal code structure to make easier to maintain (sustainability) enhancement new capability or improved behavior of existing capability
Projects
Status: Todo
Development

No branches or pull requests

1 participant