GoCD, from ThoughtWorks in Chicago, is an application lifecycle management and development tool.
N/A
The Welkin Suite
Score 9.0 out of 10
N/A
The Welkin Suite offers an integrated development environment with 105 features (and growing). The vendor aims to help you automate the chores of development, and therefore enhance your coding velocity and increase the quality of your deliverable code.
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 …
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 …
I have tried using the Developer Console, Microsoft's Visual Studio Code with the Salesforce plugins and also Mavens Mate along with Sublime. The latter is deprecated. The rest are either options that are not as fully featured as The Welkin Suite or their setup time is much …
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.
It is well suited to development-oriented projects. I find it faster to use the native Salesforce UI for more configuration projects. There are a number of tools in the suite that I have not used and probably could get more value out of it, but it has served well as my primary IDE for the last few months.
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.
It would be nice if IDE feature releases were timed to coincide with Salesforce releases (i.e. make Lightning Web Components available on the day they become available in Salesforce instances).
The IDE can be a bit buggy especially when you have several windows of the IDE open to different Salesforce instances at the same time on one machine.
Sometimes, when you click to retrieve your data too soon, before the program has a chance to ask you to connect to the instance, it can cause the IDE to freeze.
In general, when you need support there is someone there to give you an answer. I think there could be an improvement in this area, but it's hard to provide a substantial amount of support for a product that is charging roughly $15 a month. Do I feel I get more than $15 worth of support value when I need to request it? Yes.
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.
I have tried using the Developer Console, Microsoft's Visual Studio Code with the Salesforce plugins and also Mavens Mate along with Sublime. The latter is deprecated. The rest are either options that are not as fully featured as The Welkin Suite or their setup time is much greater.
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