I would recommend the tool to anyone interested in using it for the right reasons. It's very easy and useful, and depending on your use cases, it can save a lot of time. Regarding integration with other tools in our CI/CD pipeline, we have something to manage ownership control and access control for different pipelines. Spinnaker has integrated, allowing certain user groups access to specific pipelines or groups of pipelines and controlling access to deployment in different environments. Overall, based on my experience, I would rate Spinnaker nine to ten out of ten.
When it comes to the tool's integration, I would say that it does have an API. My company had to modify the APIs somewhat so that we could pass things that are specific to our processes to it, so it is not too bad. The API itself is decent enough for triggering, getting status, and exposing metrics. Integration hasn't been all that difficult. The actual installing, configuring, running, and keeping it up at scale have been the biggest issues. Integration is not too bad. I would not recommend the product to others at this point in time. If they plan to use it, I would ask them to be careful and aware of its scalability issues. If you are using Kubernetes as your application and service deployment infrastructure, I suggest you do not use Spinnaker. Considering the functionality it is supposed to provide as a workflow engine, I would rate the tool a four out of ten.
Spinnaker is deployed on-cloud in our organization. If users want to deploy docker images to the Kubernetes engines, they can choose Spinnaker. The solution's configuration setup is a bit complicated, but it is easy to use once the setup is done. It will be easy for the developers to deploy and manage applications. Overall, I rate Spinnaker a nine out of ten.
I'm a customer and end-user. We have a big environment and enough information online to help us deal with any issue that might arise. It makes for an excellent open-source option. We also have our own reliable in-house experience that has become quite useful over time. As developers, we want to deploy our code very fast, and we depend on the cloud, containers, and pipeline to get that done. Automation helps with that. Spinnaker helps with that. It's playing a significant role in making deliverables happen. I'd rate the solution ten out of ten.
Application release automation (ARA) is the process of packaging and deploying an application or software update. ARA goes from development through production. The process, and the tooling that makes it happen, brings together solutions that automate deployment, manage and model environments and coordinate releases. ARA solutions sometimes form part of the broader DevOps process.
When PeerSpot members write about their preferences for Application Release Automation software, the word...
I would recommend the tool to anyone interested in using it for the right reasons. It's very easy and useful, and depending on your use cases, it can save a lot of time. Regarding integration with other tools in our CI/CD pipeline, we have something to manage ownership control and access control for different pipelines. Spinnaker has integrated, allowing certain user groups access to specific pipelines or groups of pipelines and controlling access to deployment in different environments. Overall, based on my experience, I would rate Spinnaker nine to ten out of ten.
When it comes to the tool's integration, I would say that it does have an API. My company had to modify the APIs somewhat so that we could pass things that are specific to our processes to it, so it is not too bad. The API itself is decent enough for triggering, getting status, and exposing metrics. Integration hasn't been all that difficult. The actual installing, configuring, running, and keeping it up at scale have been the biggest issues. Integration is not too bad. I would not recommend the product to others at this point in time. If they plan to use it, I would ask them to be careful and aware of its scalability issues. If you are using Kubernetes as your application and service deployment infrastructure, I suggest you do not use Spinnaker. Considering the functionality it is supposed to provide as a workflow engine, I would rate the tool a four out of ten.
Spinnaker is deployed on-cloud in our organization. If users want to deploy docker images to the Kubernetes engines, they can choose Spinnaker. The solution's configuration setup is a bit complicated, but it is easy to use once the setup is done. It will be easy for the developers to deploy and manage applications. Overall, I rate Spinnaker a nine out of ten.
I'm a customer and end-user. We have a big environment and enough information online to help us deal with any issue that might arise. It makes for an excellent open-source option. We also have our own reliable in-house experience that has become quite useful over time. As developers, we want to deploy our code very fast, and we depend on the cloud, containers, and pipeline to get that done. Automation helps with that. Spinnaker helps with that. It's playing a significant role in making deliverables happen. I'd rate the solution ten out of ten.