Closed chirino closed 4 years ago
That is already done using github actions (they are faster than circleci)
That is already done using github actions (they are faster than circleci)
@wtrocki any pointers for the GH action?
Hi
All builds are here: https://github.com/chirino/graphql-gw/actions
Do you want to create GH actions on different project?
Hi
All builds are here: https://github.com/chirino/graphql-gw/actions
Do you want to create GH actions on different project?
The Circle CI workflow shared above seemed rich (like it can do a lot of things), was curious to see if there is already a GH action that does something similar: even though we can argue that it is mostly bash scripts and yaml files And possibly, see if I could add it in this project (to fix the issue).
My opinion:
GH action - fast reliable close to source easy to setup and extend. I haven't done any crazy stuff like starting kubernetes for tests.
CircleCI more suited for complex use cases. More docker friendly.
I started configuring GitHub ones as it is simply easier to build and manage. Linked config can be ported to GitHub actions but not sure if that will hit the limits of free quota
it's working. thx
Something like https://github.com/skupperproject/skupper-cli/blob/master/.circleci/config.yml would be handy.. Where it can also do the release builds when tags are created.