DevOps with Gearset
We’re currently trying to set up a CI/CD pipeline using Gearset. Right now, our deployment process is mostly manual — we use Gearset’s compare and deploy along with Git for version control. Our team is a mix of admins and developers.
One of the challenges we’re running into is that admins are pushing a lot of changes directly to production every day. This often leaves our sandboxes out of sync, and sometimes causes validation failures while CI jobs are running.
The manual compare and deploy process in Gearset has been very convenient for moving changes between orgs, but as we test the pipeline setup, validations and deployments are taking a very long time. It feels slower and more fragile than our current manual workflow.
I’m curious if others here have successfully set up a CI/CD pipeline using Gearset and how reliable it has been in practice.
Also, how do you handle situations where scratch orgs don’t have the same data as production? Has that caused issues with validations or deployments in your pipeline?
Any tips, lessons learned, or best practices would be really helpful.