As a reader, I can see how to apply these concepts to other pipeline providers
Opened this issue · 0 comments
chrisjsimpson commented
Is your feature request related to a problem? Please describe.
The web application is vendor neutral, but vendor lock in for CI/CD is large because it only uses Github actions (aka team foundation server).
Describe the solution you'd like
[ requires some thought ]
- Some event happens , e.g.
push/pr-open - Some reaction happens , responded to by some executor on some compute host (this was/is the general idea behind https://taskcluster.net/ , but once you start breaking the ontology down this far it perhaps becomes too abstracted )
General idea:
# all CI/CD rivers lead to yaml + bash
on: push
do: ./react-to-push.sh $@
Where ./react-to-push.sh can be executed on any executor.
At the cost of loosing some tighter integration with whichever CI/CD platform is being used
Describe alternatives you've considered
Leave other platforms as an exercise for the reader.
Additional context