Eco CI is all about understanding energy and carbon emissions of CI/CD pipelines and making this data actionable for reduction.
In some environments where CI/CD pipelines run (GitHub or GitLab SaaS products for instance) direct measurement or energy with something like RAPL or IPMI is sadly not possible.
Eco CI uses our work from our Cloud Energy project to estimate the energy used.
It was originally desgined for Github Actions and GitLab Pipelines, but has seen been made modular to work with any CI/CD system that accepts script based plugins (Jenkins, Teamcity, plain local usage etc.).
If you are on GitHub or GitLab though you can directly integrate our ready made plug-in into your testing workflow you get an automated estimation about the energy cost of the workflow run. The result is an easily integrateable Github Action where you get the energy in Joules for the CI run. It is also possible to get only results for part of the CI run.
The same logic applies for GitLab or other virtualized / containerized systems.
When using it in other local CI/CD systems that are not virtualized it works in a similar way and will output energy and carbon values of the whole system.
We believe in open source and that for advancing sustainable software the measurement tools must be freely accessible and falsifyable.
The community version gives you all the functionality for energy and carbon estimation a free open source AGPL-v3 license.
However the accompanying API & Dashboard we offer as SaaS which includes some premium features and a support plan.
The Eco CI Activity Checker was designed for CI workflows that run on a scheduled basis.
Often these run happen even if there was not even a single commit in the last ex. 24 hours, or even if there was a manual run triggered just a couple minutes before the run.
The Eco CI Activity checker skips the test run then and thus saves energy and CO2.