Tech Tip #76: Tear down CI environments after use

Your preview environments are still running from last month.

The problem

Per-branch previews, staging copies and CI runners stay up long after the work is merged. Multiple near-identical environments run in parallel for convenience.

The fix you can use today

  • Create environments on demand and destroy them automatically when a branch closes.
  • Consolidate dev, staging and QA where isolation allows.
  • Cache build dependencies instead of rebuilding from scratch every run.

Tools that help

  • GreenCode Constitution skill (GreenCode researchers): open-source energy principles and a catalogue of 37 energy anti-patterns that an AI coding agent can follow to find and fix waste like this
  • Eco CI: estimates the energy of CI pipeline runs on GitHub Actions and GitLab, per step

How GreenCode helps

GreenCode helps tackle this by mapping a running estate, rebuilding it as infrastructure as code and showing which services use the energy, including services barely running at all. More on this.

Tags

#ci-cd#cloud#idle

Sources

All GreenCode Tech Tips

  • Tip #76
  • For Ops and infrastructure
  • Category Testing, CI and code quality
  • Format short video
GreenCode

Want this checked on your own system? Talk to the GreenCode team.

Get in touch