In some cases, in terms of the Trinity feature, when it tries to communicate with AWS CloudFormation, and we try to deploy the instance or any container service, if any connectivity issues happen, the pipeline can fail. An error appears simply as a Trinity error, or some common error. It never shows exactly why it's failed and where it failed. Sometimes, we have to go and re-trigger or re-run the entire pipeline or reset the particular stage to make the deployment successful. Log-wise, we need to understand why something has failed so that we can understand and try to fix it the moment the issue is reported. The solution could use more robust monitoring. There are many features we can compare with Jenkins. For example, how the plugins are set up and how to customize things. For example, for Kubernetes, we have Grafana, and again, it's a separate tool. We'd like everything to come in a single tool and have the pipeline, its main dashboard, show us everything that needs to be monitored. For example, if you take in Jenkins, there is a feature called Blue Ocean. Over Blue Ocean, instead of console output, we can see how the stage is going. The graphics could always be better.
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...
Spinnaker's configuration setup is too complicated and should be made easy. While configuring Spinnaker, we need to get a CLI tool called Halyard.
In some cases, in terms of the Trinity feature, when it tries to communicate with AWS CloudFormation, and we try to deploy the instance or any container service, if any connectivity issues happen, the pipeline can fail. An error appears simply as a Trinity error, or some common error. It never shows exactly why it's failed and where it failed. Sometimes, we have to go and re-trigger or re-run the entire pipeline or reset the particular stage to make the deployment successful. Log-wise, we need to understand why something has failed so that we can understand and try to fix it the moment the issue is reported. The solution could use more robust monitoring. There are many features we can compare with Jenkins. For example, how the plugins are set up and how to customize things. For example, for Kubernetes, we have Grafana, and again, it's a separate tool. We'd like everything to come in a single tool and have the pipeline, its main dashboard, show us everything that needs to be monitored. For example, if you take in Jenkins, there is a feature called Blue Ocean. Over Blue Ocean, instead of console output, we can see how the stage is going. The graphics could always be better.