Ask HN: 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://ift.tt/s7bIE5O) from get go. We keep getting requests to support more CI systems on our community slack and over Github issues (https://ift.tt/AWxVLRr). 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! 2 comments on Hacker News.
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://ift.tt/s7bIE5O) from get go. We keep getting requests to support more CI systems on our community slack and over Github issues (https://ift.tt/AWxVLRr). 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!
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://ift.tt/s7bIE5O) from get go. We keep getting requests to support more CI systems on our community slack and over Github issues (https://ift.tt/AWxVLRr). 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! 2 comments on Hacker News.
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://ift.tt/s7bIE5O) from get go. We keep getting requests to support more CI systems on our community slack and over Github issues (https://ift.tt/AWxVLRr). 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!
Hacker News story: Ask HN: Should we build support for more CI platforms, or features for Actions?
![Hacker News story: Ask HN: Should we build support for more CI platforms, or features for Actions?]()
Reviewed by Tha Kur
on
April 03, 2024
Rating:
No comments: