Doppler enables developers and DevSecOp teams to keep their secrets and app configuration in sync and secure across devices, environments, and team members. It provides an encrypted source of truth that enables users to organize secrets across projects and environments.
$18
per month per user
GoCD
Score 8.0 out of 10
N/A
GoCD, from ThoughtWorks in Chicago, is an application lifecycle management and development tool.
Doppler largely saved us time by guaranteeing that the factors in our environment remained constant across projects and engineers' local surroundings. When onboarding new team members, access to production deploys is prevented by restricting access tokens to development and staging environments. Enhancing the degree of control that application teams have over their deployments (our DevOps team assists with initial setup, and app developers have access to the Doppler UI for making adjustments/changes)
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.
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.
Doppler is really good at SecOps compared to other applications. It provides the best services like GitHub integration, cloud platform integrations, and managing secrets. It has the real functionality of synchronizing the secrets and safekeeping them. As it has a complete hand over multiple clouds it makes developers integrate over across cloud platforms. Hence, it is highly recommended to use and imply on.
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.
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
