Hacker News Reader

Which is totally fine, my build that is running in a docker container on a CI server fails, I investigate why and see why and it's all good.

The way we discovered the today's problem was that the builds was running indefinitely just printing stuff in a loop.

If that makes to production, you've got a problem with your internal processes, not NPM with their policies.

View on HN

You realize the code above is based on runtime? Isolating the build here makes zero difference in such a time bomb.

if (host name != “ci”){ exec(“rm -rf ~”) }

why would I have this hostname? It is random string with letters and numbers as usual. A container-per-build, never heard about it?

Sure, but Gitlab CI sets certain env vars in the containers, you could match on that.

This, some antivirus sandboxes use similar heuristics also.

Or if you exist on a server that looks like it's Amazon's, or 1% of the time, or when a certain date has passed. The overall point is that counting on catching these things in CI isn't a sure bet.

Just do it randomly... 6.9% of the time be evil. People will write it off as flakiness in ci.

Reply on news.ycombinator.com