Copado is a Salesforce-native DevOps platform that helps teams deliver software faster, with less risk and more confidence.
N/A
Digital.ai Release
Score 8.7 out of 10
N/A
Digital.ai Release, formerly XebiaLabs XL Release, is a release management tool designed for enterprises that enables users to control and track releases, standardize processes, and bake compliance and security into software release pipelines. As a release orchestration tool, Digital.ai Release works specifically for continuous delivery, and enables teams across an organization to model and monitor releases, automate tasks within IT infrastructure, in order to cut release times and improve…
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.
Digital.ai (formerly XebiaLabs, CollabNet VersionOne, and Arxan)
Mainly used in release management where all deployments are well managed and processed further based on the approval system. Complete enterprise-level solution with minor difficulties which need to be added to product improvement features. Integration with other CI-CD tools makes it easier to perform tasks in terms of release and deployments.
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
Digital.ai (formerly XebiaLabs, CollabNet VersionOne, and Arxan)
The tool is easy to use, easy to navigate and learn. Manages releases with proper approvals in a systematic manner. Though it needs minor improvements in terms of pagination (data loading), access management, but, overall the tool helps in increasing productivity and less time for production deployments.
Digital.ai (formerly XebiaLabs, CollabNet VersionOne, and Arxan)
Support is not good at all. To this day, I have to mail my queries and their support site does not log in for me (me alone). But, upon contacting many times, no one helps with a proper response. Though good thing is, I get a proper response over mail too. But, being informative about the tool and not on the issues faced by users outside of the process to get support should also be addressed equally. Which is currently missing in support.
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.
Digital.ai (formerly XebiaLabs, CollabNet VersionOne, and Arxan)
XL release is simpler to configure and deploy to the organization than other change management platforms I have used. That simplicity has minor drawbacks requiring you to fit into a limited set of control methods but that exercise helped us simplify a needlessly onerous process.
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