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.
The SMP suite is great at what it does, but it can be very complicated to learn how to get it to do what you want. It's a beast! However, when you learn how to the things you want to do, it comes as second nature and you complete them like they're supposed to be done that way. A lot of these things are done to be able to be completed a number of different ways. Take Patch Management, you can deploy patches automatically, via Jobs, or via the "Start Software Update Cycle Now" link in the SMP Agent!
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.
The SMP solution is a beast. Each piece is complicated in itself let alone how everything ties together!
There is plenty of documentation online on how to perform a specific task, but you need to pay attention to what VERSION the article is written for. I've been halfway through implementing something only to hit a roadblock since I'm running a newer version and the option the article says to click on doesn't exist anymore...
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
Being able to report on the majority of things you want all from one interface, makes it really easy to get the results you want.
Because my employer didn't provide training, it took working with support, reading technical documentation, and just playing around on my own to learn how to do certain things.
I've had a lot of help from the SMP Support staff and they're great people and very helpful!
