Open seedstarter opened 8 months ago
Thanks @seedstarter, I know you don't have any questions but I'd love to give you some thoughts to think about as you develop this.
If I understand the proposal, for the above you'll have to capture the utilization of the processes running inside a gh action, hopefully capture the CPU name/instance type and other information so we can use the existing plugins to compute the carbon emissions of running gh actions of your CI/CD component of your applications emissions.
One thing we've thought about a lot is how to integrate IF into CI/CD workflows, a question we've asked is "is it possible within a GitHub action to run the unit tests (or some benchmark), capture the utilization and then generate a manifest file that is checked into the repo as impact.yml at the root". Imagine a world where every open source project had an impact.yml at it's root which gave information about the environmental impact of that open source project, maybe even a badge that is added to the readme like a codecoverage badge or something. We developed the SCI spec specifically so it could be used to measure open source projects so a manifest file with a pipeline to compute an SCI score would be idea. If it was as simple as, add a gh action, configure it with some params like the benchmark/unit tests/script to run and then for every commit it computed an impact.yml and checked it into the root, if it was as simple as that I can imagine many many OSS projects leveraging it. Just some food for thought, i'm not going to be one of the judges so don't take my feedback above as a guarantee the judges will like it ;) but from my perspective something that that could revolutionize the entire open source ecosystem!
Noticed this and thought I'd drop this tool I recently stumbled upon in the space of estimating energy from gh.
https://www.green-coding.io/projects/eco-ci/ https://github.com/green-coding-solutions/eco-ci-energy-estimation
I have not dove into it myself so excuse me if it is not useful, but in the hope of potentially decreasing duplicated work or increasing the depth/complexity you can pursue, I thought I'd share.
Really interested to see the results of this project.
Hello Asim and Josh,
Thank you for your suggestions. I appreciate your input and will look into it further. If I understand correctly, you want to automate the process of creating the manifest file and generating the result between different jobs of the CI/CD workflow. The final step is integrating the output IF result file into the repository. Please let me know if I misunderstood anything.
From what I can see, the links attached by Josh seem to reflect this exact functionality. I will continue to evaluate the scripts to determine how the project should be built and if I require any additional expertise (maybe looking for recruiting). Thank you again for your help.
On Thu, Mar 21, 2024 at 3:53 AM Josh Swerdlow @.***> wrote:
Noticed this and thought I'd drop this tool I recently stumbled upon in the space of estimating energy from gh.
https://www.green-coding.io/projects/eco-ci/ https://github.com/green-coding-solutions/eco-ci-energy-estimation
I have not dove into it myself so excuse me if it is not useful, but in the hope of potentially decreasing duplicated work or increasing the depth/complexity you can pursue, I thought I'd share.
Really interested to see the results of this project.
— Reply to this email directly, view it on GitHub https://github.com/Green-Software-Foundation/hack/issues/107#issuecomment-2011042013, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABXESFF4QZKTLONUVPKFETDYZI4SFAVCNFSM6AAAAABE2QSQI6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJRGA2DEMBRGM . You are receiving this because you were mentioned.Message ID: @.***>
I don't think I can participate on 2 projects at the same time, but I'd love to further this after the hackathon is over :).
Prize category
Best Plugin
Overview
The Git Actions import plugin will be designed in a way that results in retrieving data relevant to CI/CD workflows. The data acquisition process unfolds methodically, either following the completion of each individual workflow run or in bulk, addressing multiple workflows at once.
The aim is to define a spectrum of measurements and parameters essential for the seamless integration of various plugins within the impact framework pipeline.
Questions to be answered
No response
Have you got a project team yet?
I am working on this project alone
Project team
No response
Terms of Participation