The product could benefit from enhanced integration capabilities with older software systems and more customizable reporting options. Improved support for mobile devices would also be advantageous, allowing team members to access the system more effectively while on the go. In the next release, we would like to see advanced analytics features, including predictive analytics to help forecast project outcomes. Additionally, a more robust mobile app with offline capabilities would be valuable for remote work scenarios.
We have encountered stability issues lately, particularly with frequent 500 internal server errors. Despite efforts from our DevOps team to adjust settings, these issues persist, affecting our workflow, especially with machine learning data uploads. Overall, while it's beneficial for storage and accessibility, stability issues need improvement for seamless operations. The occasional occurrence of internal server errors takes several minutes to resolve on their own and can disrupt workflows. Another concern is that sometimes files appear to be successfully uploaded, but then they cannot be downloaded, with no error message indicating the issue during the upload process. This inconsistency needs to be addressed by JFrog to ensure reliable functionality for users like us.
DevOps Engineer at a tech services company with 51-200 employees
Real User
Top 20
2024-05-22T13:29:00Z
May 22, 2024
Our locations are in different environments, so the remote server takes time to catch up, causing replication delays. The engineering team suggested that this issue would be resolved, but I'm not sure if it has been addressed yet. This is more of a feature enhancement that we suggested. The technology works as expected, but the fine-tuning isn't documented in the official documentation, which has caused some issues. It's not a problem, but we could not fine-tune as needed. I hope this will be corrected and updated in the documentation for the next release.
Software Supply Chain Security is crucial for maintaining the integrity and trustworthiness of software products. It focuses on safeguarding the development pipeline from vulnerabilities and attacks.
A robust Software Supply Chain Security solution offers extensive tools for tracking, verifying, and protecting each component within the software supply chain. Experts emphasize the importance of real-time monitoring, automated compliance checks, and detailed vulnerability assessments in...
The product could benefit from enhanced integration capabilities with older software systems and more customizable reporting options. Improved support for mobile devices would also be advantageous, allowing team members to access the system more effectively while on the go. In the next release, we would like to see advanced analytics features, including predictive analytics to help forecast project outcomes. Additionally, a more robust mobile app with offline capabilities would be valuable for remote work scenarios.
We have encountered stability issues lately, particularly with frequent 500 internal server errors. Despite efforts from our DevOps team to adjust settings, these issues persist, affecting our workflow, especially with machine learning data uploads. Overall, while it's beneficial for storage and accessibility, stability issues need improvement for seamless operations. The occasional occurrence of internal server errors takes several minutes to resolve on their own and can disrupt workflows. Another concern is that sometimes files appear to be successfully uploaded, but then they cannot be downloaded, with no error message indicating the issue during the upload process. This inconsistency needs to be addressed by JFrog to ensure reliable functionality for users like us.
Our locations are in different environments, so the remote server takes time to catch up, causing replication delays. The engineering team suggested that this issue would be resolved, but I'm not sure if it has been addressed yet. This is more of a feature enhancement that we suggested. The technology works as expected, but the fine-tuning isn't documented in the official documentation, which has caused some issues. It's not a problem, but we could not fine-tune as needed. I hope this will be corrected and updated in the documentation for the next release.