Cover image for What do you use for CI/CD?

What do you use for CI/CD?

madza profile image Madza ・1 min read

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?


Editor guide

Hello Madza, Greetings from GitLab Meetup Community πŸ₯‚
I would strongly recommend GitLab CI CD. Trust me you'll love it because you have Auto DevOps & lot more on your plate, which can setup your apps entire lifecycle. So stretch your legs and lean-back, GitLab will save your time πŸ˜‡


Yep, I've used it, it's a easy and simple way to do


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 πŸ˜„


It does now I believe


+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.


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 use AWS CodePipeline and Github Actions at the company I currently work. Most of the projects are using AWS CodePipeline. I often use it in my side projects and find it quite easy to setup and monitor. The integrations you can build with other AWS and third party services are great too.


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.


In the past, I used the CircleCI to do the CI/CD and verify my projects in my company.

After the BitBucket Pipelines is released, I transfer to this because my repositories are available on BitBucket and I don't need to integrate third-party CI/CD service now :).

I usually use the GitHub Action and Travis CI to develop/contribute open source projects on the GitHub.


Been using bitbucket pipeline for almost an year. And I love it.


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.


I use the SourceHut Builds service, since everything I work on is hosted on Sourcehut too.

Works very well, and is much simpler to bootstrap than other solutions.


GitHub Actions to host the CI/CD process.

The automation itself I do in pypyr pipelines, which allows me to run the same CI/CD sequences locally as on the CI/CD server itself. This helps a lot with simplifying troubleshooting the devops itself.

So a single command runs the build/test/deploy sequence locally, and you can run the same single command on the GitHub Actions for the same effect.

Because the real work happens in the pypyr automation pipeline, this means you can jump between CI/CD hosts without a fuss, because they're really just providing the execution environment.


We moved away from self hosted jenkins to Circle CI and from there to AWS Codebuild & Code pipeline. However, for our new services we use Github Actions - it just work!
Also we were hitting webhook/repo limit (which is 20 I believe) and we were able to solve that issue using the Github Actions too.


I use GitHub Actions. Since I'm already using GitHub, using Actions for CI/CD means one less system to keep track of.


I use this workaround that works well on any git repository such github, gitlab, bitbucket and so


We use TeamCity. It has been very reliable so far and has been a breeze to setup.



Using bitbucket pipelines. Beeing excited how ez it is to have CI/CD :-)


For pet projects - Github Actions, Github Packages or Travis CI
For projects on my job - Jenkins, AWS CodeBuild, AWS CodePipeline


Jenkins X and Github actions mostly πŸ˜„


Mostly Azure DevOps, but GitHub Actions for many smaller projects.


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


CircleCI and codecov for test coverage


right now I'm using CircleCI, though I'm tempted to build my own


At work I use Azure pipelines. In my personal projects I just started using GitHub actions.


I'm using Github, Mina and Codeship and never have had problems


Circle CI and Github Actions. In the past, Bitbucket Pipelines. Circle is way too unstable...


Azure/VSTS free to get started, easy and massively scalable.


drone πŸ€–

I πŸ’š it's extensibility and scalability


Company: Azure devops.
Personal: Github actions, Travis.


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.


I used Gitlab CI/CD. Easy to use and clear documentation.