Craft.io vs. GoCD

Craft is really well suited for any size design team - I have used it within a team of 3, and within a team of 30. It helps with collaboration within the team, and between external teams through 'sync' with Invision. It increases efficiency of using Sketch with things like 'data', 'duplicate', and 'stock'. These tools not only make designing faster, but also more realistic, allowing us to 'test' our designs sooner.

Incentivized

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.

Incentivized

• Craft is built to digital products developers, so its workflow is great.
• It has a very nice interface and is a beautiful tool.

Incentivized

• 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.

Incentivized

• Wish there was a way to export a graphical view of the story map.
• Sometimes the side navigation panels get in the way.

Incentivized

• UI can be improved
• Location for settings can be re-arranged
• API for setting up pipeline

Incentivized

I never had to use Craft support.

Incentivized

Craft has a completely unique tool set that has functionality that really is not duplicated any where else in the industry. It cannot really be compared to any other tool I have had experience with, especially with the larger cloud infrastructure that Invision has built around their plugin and their platform.

Incentivized

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.

Incentivized

• It was good for tying end-user feedback on the app store to feature requests and help justify investments.

Incentivized

• ROI has been good since it's open source
• 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

Incentivized