Copado vs. ServiceNow DevOps

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.

Incentivized

ServiceNow DevOps is suitable for IT companies that are medium to large, It is great when it comes to keeping a track of all the activities, it takes a very little amount of time for creating tickets, with a small amount of information. It is a good tool for incident management, and change management. It will be less suitable for small-scale companies.

Incentivized

• Capturing latest changes accurately in the commit window
• Auto resolving conflicts
• gate checks for apex code coverage.
• Giving insights into the validation errors
• very easy to migrate data & metadata between orgs, just with few clicks

Incentivized

• Plan develop, build, test, deploy and operate any applications in a safer environment.
• Evaluating and monitoring improvements
• Connects with third party and existing applications

Incentivized

• In deployment, the Query can be lost when editing, which can cause a lot of problems.
• The Query option is cumbersome, but it works!
• The deployment instructions fields could be made into rich text fields which would be awesome.

Incentivized

• No drop-down option is available to click when requesting specific software or hardware.

Incentivized

very good user interface. It has reduced tons of manual efforts for the developers. Very easy to validate the release work. Easy to club multiple stories into one deployment. We can integrate Copado with our JIRA and all the PR’s are visible under the user story on JIRA board. But this can be overwhelming for beginners

Incentivized

There are tools such as ANT migration tool or using sfdx but Copado makes the deployments super simple. If a user is not that technically strong still he can use Copado and deploy the changes in a few clicks. Copado provides a complete package of maintaining the development and repositories in a common platform. There are pipelines that you can set that changes will move from which org to the final org in a very organized manner. We can perform static code analysis at the time of deployment of the changes and we have to clear those if we need to deploy the changes. Creating pull requests is super easy and can be managed by Copado itself. Overall a superb managed package for deployment in Salesforce.

Incentivized

As mentioned previously, not sure if ServiceNow DevOps can handle tickets in an agile methodology, where everything is setup based on Sprints, stories and the whole agile terminology. We use OpsGenie to setup shifts for Production support teams, OpsGenie alerts people through a mobile app about production issues as well as to whom is Oncall support for multiple teams. Not sure this functionality is there in ServiceNow DevOps. For now those 3 applications are handling different functions in our company and would be difficult for me to compare them

Incentivized

• 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

Incentivized

• ROI
• Increased the NPR score.
• Central locale for information and troubleshooting.

Incentivized