In DevOps, a continuous and automated delivery cycle is the backbone that makes fast and reliable delivery possible.
What do you use for CI/CD?
In DevOps, a continuous and automated delivery cycle is the backbone that makes fast and reliable delivery possible.
What do you use for CI/CD?
For further actions, you may consider blocking this person and/or reporting abuse
Oldest comments (37)
I've been using Gitlab CI and liking it a lot. I can even configure a remote Runner on a VPS and never touch the free tier limits.
You got me man 😉
GitLab wishes you a happy CI CD 🦾
I was using CircleCI at my previous company. It's definitely reliable, but one thing I didn't like was how hard it was to manage and update 20+ different builds. I am now working on a project on my own and using Github Actions because it's free. It's been a great experience so far. I love having everything right inside of Github.
GitHub Actions. It does everything I need, but I would like it if it supported global secrets, as I often have to create the same secrets on multiple projects.
"one PAT to rule them all" ... can relate 😄
+1 You're now able to create secrets at the org level and reference them across all of your repos.
this is why you have terraform/pulumi .... Also I have strong believe that CD/CI should be stored in git anyway!
GitLab CI, works perfectly for my team.
Buildkite
Jenkins - you just can't beat it's flexibility.
I especially like the fact that I can add logic right into my pipeline without having to create separate scripts to achieve this.
We use Azure devops. Becaus we are develop ms stuff. But it can be used for other Systems too.
Also there you can use separate Module, so you can host source on github and CD it with devops
drone 🤖
I 💚 it's extensibility and scalability
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.
Company: Azure devops.
Personal: Github actions, Travis.