HN
login
Effort to reduce wasted compute and move towards a greener future

.Hello All, while working on my startup I released that even a small coding change was triggering the whole ci / cd pipeline and wasting my runner time, to solve this problem I thought about developing a tool to…

2 points•adityankale1995•10 days ago•3 comments•
#greener#compute#reduce#effort#towards#future#wasted#reduce wasted
.Hello All, while working on my startup I released that even a small coding change was triggering the whole ci / cd pipeline and wasting my runner time, to solve this problem I thought about developing a tool to fix it. Later on I realized that more developers might be facing this issue. I have made the tool open source and would like to know your thoughts about this idea

3 comments

brudgers9 days ago
If it meets the guidelines, this might make a good 'Show HN'. Show HN guidelines: https://news.ycombinator.com/showhn.html
gus_massa9 days ago
In GitHub it is possible to run configure so some of the test run only if some files changed.
thedefaultman9 days ago
The boring fix is usually already in the forge. On GitHub Actions, `paths` / `paths-ignore` on the workflow, or a changed-files filter job that gates the expensive matrix, stops a one-line docs edit from waking the full pipeline.

In a monorepo, path filters alone are not enough. You want an affected graph (packages and tests), fail-closed when the graph is unsure, and a canary on main that still runs the full suite. Unsure means run it. Unsure means skip it is how you ship a lie.

I would not start with a new product for this. Instrument where minutes go (checkout, setup, build, test), tighten the trigger graph, then decide if anything is still left.

Read the full thread on Hacker News →

Related stories