GoCD vs. Pulp

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.

Incentivized

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

I understand that this tool may not be for everyone, but it served its purpose perfectly for us. It allows us to safely change to older repositories in case we need to roll back any changes. It has definitely reduced operational costs for us due to allowing us to safely manage our own packages without relying solely on external providers, which are not always reliable. However, it's worth mentioning that the setup/maintenance can be a little bit fiddly for some users. There's a learning curve here, but, to us, it was totally worth it.

• 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.

Incentivized

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

• UI can be improved
• Location for settings can be re-arranged
• API for setting up pipeline

Incentivized

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

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.

Incentivized

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

• ROI has been good since it's open source
• 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

Incentivized

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info