GoCD is easy to set up. So if you just want to get some pipelines up & running quickly, & they're quite stable, or you can have many pipelines for different needs then GoCD is great. Still, if you only want to have a few pipelines, but with the flexibility to run them with different parameters dynamically, then Jenkins is better.
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.
I prefer using GoCD compared to Jenkins. The UI makes sense, I like the simplicity to hit the 'Play' button for a straightforward deployment of the 'Play +' if you need to override some settings when deploying whereas Jenkins, you have the whole page for each pipeline. The environment makes sense but can often confuse the user while GoCD simply has a drop-down to select your environment.
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
