Senior Software Engineer at a financial services firm with 10,001+ employees
Real User
Top 20
2025-04-28T09:03:00Z
Apr 28, 2025
When deploying multiple components to multiple environments, like production and BCP, failures sometimes occur. Improvements are needed when deploying one component to one environment.
Previously, when deploying a version that had been deployed successfully before, it sometimes failed upon trying again, which seems to be an intermittent issue about stability. I prefer the previous less compact UI version of Harness, which showed more details on the screen.
Even with automation, there's a requirement for manual change requests for approvals. If this is corrected, we could have a totally automated pipeline. Otherwise, we need to use GitLab or GitOps to trigger automatically with every commit.
Engineering Technical Leader - SRE (Cloud/Kubernetes-Security) at Cisco
Real User
Top 10
2024-04-05T11:42:52Z
Apr 5, 2024
The platform's initial setup process could be simplified. Additionally, security features and capabilities for understanding vulnerabilities within the application could be enhanced directly from the tool. There's also room for improvement in debugging pipeline issues, which can sometimes become complex. Limitations regarding reconciliation features and support for certain parts of the infrastructure should also be addressed.
Harness offers a comprehensive toolset for automating deployment processes and enhancing software update efficiency. It's lauded for its CI/CD capabilities, feature flagging, and real-time deployment monitoring. Key features include an intuitive UI, secret management, and robust rollback functionalities, all contributing to improved productivity and reduced errors in DevOps environments.
Harness setup and configurations could be made easier to configure, which would be helpful.
When deploying multiple components to multiple environments, like production and BCP, failures sometimes occur. Improvements are needed when deploying one component to one environment.
Previously, when deploying a version that had been deployed successfully before, it sometimes failed upon trying again, which seems to be an intermittent issue about stability. I prefer the previous less compact UI version of Harness, which showed more details on the screen.
Even with automation, there's a requirement for manual change requests for approvals. If this is corrected, we could have a totally automated pipeline. Otherwise, we need to use GitLab or GitOps to trigger automatically with every commit.
The platform's initial setup process could be simplified. Additionally, security features and capabilities for understanding vulnerabilities within the application could be enhanced directly from the tool. There's also room for improvement in debugging pipeline issues, which can sometimes become complex. Limitations regarding reconciliation features and support for certain parts of the infrastructure should also be addressed.