What I'd like to see is a CI/CD engine backend. Most CI/CD solutions have relatively the same feature set:
- Code builds
- Code deploys
- Git Hooks
- Parallel builds
- Matrix builds
- Build as configuration
- Etc
If there were an engine that supported these features, the community could create a number of frontends that target their specific needs.
Jenkins was held back, in my opinion, for a number of years by its antiquated UI. And while Jenkins does have an API of sorts, writing a new UI for it is not a simple task.
I've used Drone for a while, and it gets a lot of these things right, but at the end of the day it is a holistic, integrated solution.
I'd like to see a composable, modular CI/CD framework.
and default ancillaries for secrets, artifacts, alerts, etc., with the idea that they could all be replaced with a purpose-built product that's actually good at it (i.e. Vault, Artifactory, PagerDuty/Sensu/whatever)
I think deployment is a separate problem space to CI and shouldn't be included
- Code builds
- Code deploys
- Git Hooks
- Parallel builds
- Matrix builds
- Build as configuration
- Etc
If there were an engine that supported these features, the community could create a number of frontends that target their specific needs.
Jenkins was held back, in my opinion, for a number of years by its antiquated UI. And while Jenkins does have an API of sorts, writing a new UI for it is not a simple task.
I've used Drone for a while, and it gets a lot of these things right, but at the end of the day it is a holistic, integrated solution.
I'd like to see a composable, modular CI/CD framework.