Likelihood to Recommend IBM UrbanCode Deploy is excellent for code deployments such as Java, .Net, C++, etc. It can also deploy and run SQLs reasonably well. Where it lacks is the ability for executables, Jars, WARs, EARs, etc.
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 Consistently deploys to multiple environments with no changes to the process. Having reusable processes across environments from Dev to Production make deployments more consistent and easier to manage. IBM UrbanCode Deploy has an easy to understand UI, to be able to review if a deployment has successfully completed or not, and details if it did not work. Using the UI is simple and easy to understand. Scheduling and approvals are built-in as configured for the deployments. This allows us to use the same deployment process, but get approvals as needed when code is moved up to the upper environments. 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 IBM UrbanCode Deploy does code deployments easy enough, but configurations or ex deployments are a little more complicated. I work on packaged systems, so most of the code I get is form a vendor that I have to deploy. IBM UebanCode Deploy integration into the mainframe world would be ideal. My company uses Mainframe and OpenSystems technologies, and many times there are dependencies between the deployments. 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 Support Rating I've not worked directly with IBM UrbanCode Deploy support. My DevOps team administers the environment and deals with that.
Read full review Alternatives Considered • 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 IBM UrbanCode Deploy has had a positive impact on making deployments much easier and quicker to do. Downtime for a system is greatly reduced and deployments go much smoother as the processes are complete repeatable and not manual. 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