Likelihood to Recommend When we have a large organization and number of changes and deployments are more than we should go for Copado. As we know it is a paid managed package and the cost is high so for dealing with fewer deployments it is not preferable to buy. Copado is well suited for users who don't have much technical understanding. So those users can see the User interface select the changes that need to be deployed by selecting the metadata. From Git operation to deployment all is handled by Copado itself. Copado has reduced the efforts for creating the package.xml and direct deployments can be done within a few clicks. Another Major aspect is that it can be directly synced with Jira or Azzure board from where the user stories will be synced and actions can be performed accordingly. For small organization, Copado can be expensive and to set up and maintain we need a technical person to do so.
Read full review Spinnaker suits well for applications which are stateless and can adapt to an immutable architecture of deployment. But for applications which are stateful and cannot afford to spin up new servers for every deployment doesn't go well with Spinnaker. It can handle only deployments which are VM based and cannot support deployments to serverless architecture like AWS Lambda etc.
Read full review Pros Metadata Deployments Data Deployments Salesforce CPQ deployments that require a lot of various Data Transferring deployments between teams. Read full review Fast deployments. Can be integrated with a good variety of other products. Also provides some insights from your environment. Read full review Cons Back promotions are sometimes difficult and behave in a weird manner After the deployment to production next changes in the pull request shows all the changes from the previous release as well Cannot be used through mobile Read full review It does NOT support CFN based deployments Windows based systems finds it difficult to onboard to Spinnaker. Pipeline level access authorisation is not there. Support for EBS volume encryption is probably missing. Attach/detach EBS volumes during deployments is difficult. No support to deploy the artifacts without re-creating the servers. Only pure immutable deployment are allowed. Open-source - so good and bad! Spinnaker on its own has 10 underlying micro services. Managing Spinnaker needs a focussed platform approach. User authentication is easy but authorisation management is not straight forward. Debajit Kataki Sr. Devops Mgr. ( Tools, automations , Release Engineering/ CICD , AWS )
Read full review Alternatives Considered Flosum is a downgrade for sure and I do not recommend it. Gearset is an upgrade and my preferred solution. Gearset has simplified the deployment path and makes it very easy to move between Salesforce instances. If there are any difficulties with Gearset they also have the best customer support for any deployment tool I've tried. Overall I'd say Gearset is #1, Copado #2 and Flosum a distant #3.
Read full review • Pipeline Expressiveness • Self-Service/Override • Visibility of Client Teams • Operability of Client Teams - • High-Quality Integrations (AWS, IHP, Google) • Extensibility – (Ability to add code) • The maturity of Deployment Process • Speed/Ease of Onboarding
Read full review Return on Investment It has reduced the efforts to create package.xml manually and deploy the changes Another positive impact is that we can track the commits to which org they have reached in an organized way and we don't need to maintain them separately For setting Copado it take a lot of time and training is required for the complete setup which is time-consuming Read full review By using Spinnaker we are able to deploy new versions of our product quickly. A deployment takes in average 2 minutes. Our investment on Spinnaker was just time learning it. Read full review ScreenShots