https://github.com/teleivo/dhis2-github-action-metrics

Analysis of GitHub actions usage in https://github.com/dhis2/dhis2-core using https://github.com/teleivo/github-action-metrics
https://github.com/teleivo/dhis2-github-action-metrics

ci github-action github-actions metrics

Last synced: about 8 hours ago
JSON representation

Analysis of GitHub actions usage in https://github.com/dhis2/dhis2-core using https://github.com/teleivo/github-action-metrics

• Host: GitHub
• URL: https://github.com/teleivo/dhis2-github-action-metrics
• Owner: teleivo
• License: mit
• Created: 2021-10-28T06:53:23.000Z (about 3 years ago)
• Default Branch: main
• Last Pushed: 2024-10-24T19:43:30.000Z (15 days ago)
• Last Synced: 2024-10-24T20:13:08.001Z (15 days ago)
• Topics: ci, github-action, github-actions, metrics
• Homepage:
• Size: 59 MB
• Stars: 0
• Watchers: 3
• Forks: 0
• Open Issues: 1
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# DHIS2 GitHub Action Metrics

I started this project to analyze the test workflow we use at

[DHIS2](https://dhis2.org/about/). I wanted to know where time was spent, why

some test runs took 15min while others took 23min to finish. How could we get

faster feedback on PRs and reduce this variation in test duration?

Using [GitHub action metrics](https://github.com/teleivo/github-action-metrics)

I

- fetch(ed) [GitHub action data](https://docs.github.com/en/rest/reference/actions) every day using

  [a scheduled GitHub action](./.github/workflows/fetch_actions.yml). The data is

  then stored in this repository. This way I can accumulate a history of our

  workflow runs.

- indexed and analyzed the data using Elasticsearch and Kibana