GoCD, from ThoughtWorks in Chicago, is an application lifecycle management and development tool.
N/A
Google Kubernetes Engine
Score 8.0 out of 10
N/A
Google Kubernetes Engine supplies containerized application management powered by Kubernetes which includes Google Cloud services including load balancing, automatic scaling and upgrade, and other Google Cloud services.
$0.04
vCPU-hr Autopilot Mode
Pricing
GoCD
Google Kubernetes Engine
Editions & Modules
No answers on this topic
Autopilot Mode - 3 year commitment price (USD)
$0
GKE Autopilot Ephemeral Storage Price GB-hr
Autopilot Mode - 1 year commitment price (USD)
$0.0000438
GKE Autopilot Ephemeral Storage Price GB-hr
Autopilot Mode - Regular Price
$0.0000548
GKE Autopilot Ephemeral Storage Price GB-hr
Autopilot Mode - Spot Price
$0.0000548
GKE Autopilot Ephemeral Storage Price GB-hr
Autopilot Mode - Spot Price
$0.0014767
GKE Autopilot Pod Memory Price GB-hr
Autopilot Mode - 3 year commitment price (USD)
$0
GKE Autopilot Pod Memory Price GB-hr
Autopilot Mode - 1 year commitment price (USD)
$0.0039380
GKE Autopilot Pod Memory Price GB-hr
Autopilot Mode - Regular Price
$0.0049225
GKE Autopilot Price GB-hr
Autopilot Mode - Spot Price
$0.0133
GKE Autopilot vCPU Price vCPU-hr
Autopilot Mode - 3 year commitment price (USD)
$0.02
GKE Autopilot vCPU Price vCPU-hr
Autopilot Mode - 1 year commitment price (USD)
$0.0356000
GKE Autopilot vCPU Price vCPU-hr
Autopilot Mode - Regular Price
$0.0445
vCPU Price vCPU-hr
Standard Mode
$0.10
per hour
Cluster Management
$0.10
per cluster per hour
Cluster Management
$74.40 monthly credit
per month per hour
Standard Mode - Free Version
Free
per hour
Offerings
Pricing Offerings
GoCD
Google Kubernetes Engine
Free Trial
No
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
GoCD
Google Kubernetes Engine
Features
GoCD
Google Kubernetes Engine
Container Management
Comparison of Container Management features of Product A and Product B
Previously, our team used Jenkins. However, since it's a shared deployment resource we don't have admin access. We tried GoCD as it's open source and we really like. We set up our deployment pipeline to run whenever codes are merged to master, run the unit test and revert back if it doesn't pass. Once it's deployed to the staging environment, we can simply do 1-click to deploy the appropriate version to production. We use this to deploy to an on-prem server and also AWS. Some deployment pipelines use custom Powershell script for.Net application, some others use Bash script to execute the docker push and cloud formation template to build elastic beanstalk.
If your application is complex, if it's planet-scale, or if you need autoscaling, then Kubernetes is best suited. If your application is straightforward, you can opt for App Engine or Cloud Run. In many cases, you can prefer to run the cloud on GKE. But once you deploy on Kubernetes, you get the flexibility to try different things. But if you don't seek flexibility, it's not an option for you.
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.
Engine upgrade rollout strategy - well documented and configurable
Integration with other Google Cloud services like the Compute Engine, SaaS databases, and some cloud networking like Cloud Armor
Graphical interface for a lot of operations - either for a quick peek/overview or actual work done by administrators and/or developers (via the Google Cloud Console, for example)
Very good Kubernetes distribution with a reasonable total price. Integration with storage and load balancer for ingress and services speed up every process deployment.
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 input the parameters.
GKE spins up new nodes a LOT faster than AKS. GKE's auto scaler runs a lot smoother than AKS. GKE has a lot more Kubernetes features baked in natively.
When issues came up, we reached out to some folks at GCP and they seemed to be very prompt and attentive to our needs. They were always willing to help and provide additional details or recommendations or links to resources. This kind of support is very helpful as it allows us to navigate GKE with more confidence.
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