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.
You will like DataGrip; it is the best software to channel and influence data systems and efficiently. It will help you be more efficient and productive in exporting computer data; it is very effective. There are no errors, and you will feel comfortable using them. It promotes data quality and has excellent graphics to represent your information through statistical processes.
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.
Usability has two aspects, being a complete tool and being easy... DataGrip has a lot of features but it is big, not clear how to use most of the things and most people won't need them. In my opinion, usability is good enough but not friendly.
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.
DataGrip provides a single UI for many DBMS platforms, instead of using one for each. Because of that, you can migrate things between platforms using the tool and "look across" all databases at once.
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
