<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Green-Devops on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/green-devops/</link><description>Recent content in Green-Devops on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 10 Jul 2026 11:00:57 -0500</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/green-devops/index.xml" rel="self" type="application/rss+xml"/><item><title>Green DevOps: Adding carbon measurement to CI/CD pipelines with Eco CI and Carmen</title><link>https://curadevops.metacog.co.kr/insights/2026-07-10-green-devops-why-carbon-measurement-belongs-in-your-ci-cd-pi/</link><pubDate>Fri, 10 Jul 2026 11:00:57 -0500</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-10-green-devops-why-carbon-measurement-belongs-in-your-ci-cd-pi/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Learn:&lt;/strong> Introduces an emerging practice of per-pod and per-pipeline emissions visibility, which could inform infrastructure sizing decisions, but no operational urgency and no signals anchoring an action today.&lt;/li>
&lt;li>&lt;strong>CI/CD — Learn:&lt;/strong> Eco CI and Carmen are wirable into existing GitLab pipelines today as lightweight integrations, worth evaluating as a team sustainability metric, but no deprecation, supply-chain risk, or deadline makes this actionable now.&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Relevant for teams building ESG or sustainability reporting into engineering KPIs, but no licensing change, cost impact, or vendor risk forces a strategic decision — shapes future golden-path thinking only.&lt;/li>
&lt;/ul></description></item></channel></rss>