I usually use GCB (Google Cloud Build) for CD because I'm having a hard time giving secrets to the 3th party.
Because I Still didn't figure out how to have the output of GCB in GitHub action tab when creating PR, we use GitHub actions for mainly CI stuff, like unittests/e2e/lint etc...
Also, GCB is cool because you can bring your own docker-compose and basically run there whatever you want! Something that every CD/CI should have in my opinion.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I use a combination of GitHub Actions and Google Cloud Build (cloud.google.com/cloud-build).
Actions deploys the web app to Vercel and runs code scans. Cloud Build tests, builds and deploys the Google Cloud Platform services.
same here! Or almost...
I usually use GCB (Google Cloud Build) for CD because I'm having a hard time giving secrets to the 3th party.
Because I Still didn't figure out how to have the output of GCB in GitHub action tab when creating PR, we use GitHub actions for mainly CI stuff, like unittests/e2e/lint etc...
Also, GCB is cool because you can bring your own docker-compose and basically run there whatever you want! Something that every CD/CI should have in my opinion.