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
Top comments (38)
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 😇
about.gitlab.com/blog/2019/07/12/g...
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 😄
+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!
It does now I believe
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.
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 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.
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 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.