HACKER Q&A
📣 igorzij

Should we build support for more CI platforms, or features for Actions?


Currently, Github Actions is de-facto the only fully supported CI platform in Digger, we’ve been building it as a CI-agnostic tool (https://github.com/diggerhq/digger) from get go. We keep getting requests to support more CI systems on our community slack and over Github issues (https://github.com/diggerhq/digger/issues/81).

Unlike other automation tools for Terraform, Digger doesn’t run jobs on the server; instead it uses your CI (like Actions) as a compute backend. This is more secure and also much cheaper if you use your own runners in your CI.

But each CI and each VCS is ever so slightly different; and we are now at a crossroads - Should we build support for more CI platforms, or more features for GitHub Actions? We’d love any thoughts/inputs!

  👤 codingdave Accepted Answer ✓
> "We keep getting requests to..."

If you are getting consistent feedback from your customer base that they desire a feature, why would you second-guess that feedback by asking a different group of people if they agree?

👤 brudgers
We keep getting requests to support more CI systems on our community slack and over Github issues

Give people a price for the feature they request. The price should reflect the costs of future support. And of course overhead and profit.

Good luck.