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.
S4 for Salesforce is the best platform for large recruiting firm for recruitment processes and a lot of candidates. CRM provide the best solution for any recruiting firm. Salesforce is well suited in our company because it allows recruiters to store the data of every and each candidate in our system and also we don't have the fear of loosing the data.
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.
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.
In S4 for Salesforce highly integrated with salesforce ecosystem. Salesforce gives capabilities for candidate and client management. In Adapt Bullhorn: Bull horn does not have built in integration. but if provides its own CRM. In SS4 for Salesforce: you can edit, customize the UI according to your needs. In Adapt Bullhorn: it also provides you the customizable Interface but not as much as Salesforce
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
