-
Notifications
You must be signed in to change notification settings - Fork 14
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
[Action] Tracking the energy consumption of GitHub Actions Pipelines #55
Comments
Thanks for mentioning our tooling @by-d-sign ! We are very happy to make a PR for a project of your choice. We wil integrate it on a fork and then generate some data so you have an idea how it looks like. Which project shall it be? @nikimanoledaki @by-d-sign :) |
Sounds like a great subject for a blog post @by-d-sign @ArneTR 😉 https://github.com/cncf/tag-env-sustainability/issues/new?assignees=&labels=blog&projects=&template=blog.md&title=%5BBLOG%5D+%3Cblog-title%3E |
As we agreed during the WG regular meeting this is out of scope for the current milestone, thanks for adding the issue. We will circle back with a proposed action time after the KubeCon when we will have time to organize and prioritize issue for the next milestone. Info about the milestones are currently in the readme |
I made a demo of how this would look for one of the workflows from Falco. I picked the only one that had a cron, as this shows the most simple integration:
Additonal: @by-d-sign Eco-CI can also handle matrix/parallel Github Actions out of the box. Since you brought this up as a question in one of the last community meetings :) |
Hey folks, I hope you had a great KubeCon. We have recently added some features to our Eco-CI tooling. Now it shows also the location of the running machine which then enables to include grid intensity as well as total CO2e emitted. You can see it in this sample PR that we have made on a fork from the Falco repository. Aggregation and timeline data is provided here: https://metrics.green-coding.io/ci.html?repo=green-coding-solutions/falco&branch=2/merge&workflow=87453986 Hope this ping is interesting for you :) @ribalba: Looping you in |
Hey folks, after I month I thought I give this a gentle ping. Any update if you fancy to integrate Eco-CI into any projects? We are super happy to help and provide a PR. Integration effort should be minimal. We recently also approached other open source projects and can provide ready tested PRs. Example : NMF-earth/nmf-app#393 While doing so very often also some direct optimizations come into view. Example where we did this with NMF: NMF-earth/nmf-app#395 |
Hi @ArneTR! A PR is very much welcome. If you get stuck:
We are working on some Github Action pipelines as part of two proposals being written right now. One is open for a review, for an idea of how we'll be using GA pipelines: #88 - also feel free to review if you'd like! Looking forward to reviewing your PR 👍 😊 |
Hey @nikimanoledaki what I would need is a point which repo you find most suitable. You have quite many in the CNCF :) In the history of this Issue I already pointed to a sample integration for Falco (See here) Which was however a very small pipeline and just for demo purposes. So a pointer would be nice for a repo:
I will make a PR then and tag you there |
Would you consider submitting this to https://github.com/opensearch-project/OpenSearch/ ? It's a beefy build that takes a long time and runs a lot. |
Hey @wbeckler, sure! Which of the pipelines do you have in mind? Project has quite many apparently :) |
Hey @nikimanoledaki @leonardpahlke @wbeckler @by-d-sign Since I get no reply on my last message I thought I go ahead and just pick the biggest workflow and make a sample integration there. Here is the PR: opensearch-project/OpenSearch#14450 I also tagged you there. The implementation features the newest Eco-CI with minimal overhead (https://github.com/green-coding-solutions/eco-ci-energy-estimation/releases/tag/v4.0-rc3) but I refrained from integrating stuff like PR-Comments as this would require workflow permissions changes and I wanted to keep it slim. Happy for your feedback! |
Pipelines are not only a great tool for automating tedious tasks, they are also probably a mayor energy consumer. Optimizing them could be worthwhile, however their actual energy demand is currently neither visible nor well researched.
Eco-CI is an approach to measure/estimate the energy consumption of a GitHub Actions Pipeline. This could be a great tool to raise awareness and a first step towards optimization.
The text was updated successfully, but these errors were encountered: