What do you like best?
a. Mapping to Real World Concepts.
Example : Environment: I can group all my servers into different buckets/environments namely DEV, QA, STAGE, PROD. This make organizing and assigning machines and pipelines easy.
b. The User Interface is easy.
c. Capability to deploy a script to multiple machine
d. EASY to Learn, and provide transition to a team member.
e. The support team is very very quick to respond.
What do you dislike?
a. When the disk space is very very low (to store the GO artifacts), there is an option to delete the oldest artifacts. But, sometimes, I dont want to delete the older artifacts, rather I want the DEV-Trunk artifacts to be deleted. It would be nice to have an option to mention the GROUP name whose Artifacts will be deleted.
Also, A email trigger would have been better if the disk space reduces to limit-X.
b. My project has 100s of pipelines. On Dashboard each GROUP has a list of pipelines. I would like to expand and shrink the Group by double-clicking it. Rather now, I have scroll a lot to find pipelines.
Recommendations to others considering the product:
1. I liked it, and I migrated an complex application from Jenkins to GO. My Development team enjoys it, and they cant believe this kind of continuous Integration can be achieved very quick
2. If you desire to achieve continuous Integration and Delivery, use this product.
What problems are you solving with the product? What benefits have you realized?
We are a Java shop, and we use GO to deploy 20 major applications involving more than 200 servers.
The greatest benefit I see is, its UI an conceptualization is cleared designed in way, the knowledge transition of an application deployment is very very easy and smooth.