aqua cloud is an AI-powered test management system designed specifically for regulated industries and big enterprises that aims to help to accelerate audit processes and speed up releases.
N/A
GoCD
Score 8.0 out of 10
N/A
GoCD, from ThoughtWorks in Chicago, is an application lifecycle management and development tool.
N/A
Pricing
aqua cloud
GoCD
Editions & Modules
aqua cloud
Contact Us
per month per user
aqua enterprise cloud
custom price quote
No answers on this topic
Offerings
Pricing Offerings
aqua cloud
GoCD
Free Trial
Yes
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
*plus 20% for Maintenance & Support
—
More Pricing Information
Community Pulse
aqua cloud
GoCD
Considered Both Products
aqua cloud
Verified User
Anonymous
Chose aqua cloud
I use aqua ALM for test cases. It has got the integration with JIRA. Best thing is it will surely very well connect the organization in only one hub. I will perform test case, use cases.It has got open-source & many tools in one platform. Aqua ALM will our organization to …
GoCD is easier to setup, but harder to customize at runtime. There's no way to trigger a pipeline with custom parameters.
Jenkins is more flexible at runtime. You can define multiple user-provided parameters so when user needs to trigger a build, there's a form for him/her to …
I prefer using GoCD compared to Jenkins. The UI makes sense, I like the simplicity to hit the 'Play' button for a straightforward deployment of the 'Play +' if you need to override some settings when deploying whereas Jenkins, you have the whole page for each pipeline. The …
1. I used this to do test cases, wherein I got the results with visuals. I explained to clients very well with the visual examples as well. 2. Even I was very new to this tool, it gave me the best company. Even while integrating components as a beginner. 3. Even if I have got any bugs in test cases, it helped me to resolve in a better way. Happy user me! Thanks Aqua ALM.
GoCD is easy to set up. So if you just want to get some pipelines up & running quickly, & they're quite stable, or you can have many pipelines for different needs then GoCD is great. Still, if you only want to have a few pipelines, but with the flexibility to run them with different parameters dynamically, then Jenkins is better.
Pipeline-as-Code works really well. All our pipelines are defined in yml files, which are checked into SCM.
The ability to link multiple pipelines together is really cool. Later pipelines can declare a dependency to pick up the build artifacts of earlier ones.
Agents definition is really great. We can define multiple different kinds of environments to best suit our diverse build systems.
I use aqua ALM for test cases. It has got the integration with Jira. Best thing is it will surely very well connect the organization in only one hub. I will perform test case, use cases.It has got open-source & many tools in one platform. Aqua ALM will our organization to manage, plan and to execute the use cases incidents in clear manner, it also fetches the reports which we give input. By this, we will also download the FLOW reports, visual diagrams. Happy clients! They appreciated my project.
I prefer using GoCD compared to Jenkins. The UI makes sense, I like the simplicity to hit the 'Play' button for a straightforward deployment of the 'Play +' if you need to override some settings when deploying whereas Jenkins, you have the whole page for each pipeline. The environment makes sense but can often confuse the user while GoCD simply has a drop-down to select your environment.
Once I was working on my project's use case incident, I wanted the result to get in tree view, but I didnt get. Visuals I got, not which is the one I wanted. Anyways I explained the same to clients. so I would highly like the AQUA team to improve this.
I really wanted to appreciate that bug reporting in use case incidents. Very good!
In one of the projects I wanted to work in the FLOW DIAGRAM VISUAL. I got the excellent result in this. Thank you again :)
Settings.xml need to be backed up periodically. It contains all the settings for your pipelines! We accidentally deleted before and we have to restore and re-create several missing pipelines
More straight forward use of API and allows filtering e.g., pull all pipelines triggered after this date