When comparing GoCD vs Bitbucket Pipelines, the Slant community recommends GoCD for most people. In the question“What are the best continuous integration tools?” GoCD is ranked 18th while Bitbucket Pipelines is ranked 22nd. The most important reason people chose GoCD is:
GoCD supports pipelines natively. This way you can build your projects by pipelining them.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Native support for pipelines
GoCD supports pipelines natively. This way you can build your projects by pipelining them.
Pro Good traceability of what contributed to a given artifact
GoCD's LEAN value stream UI helps all stakeholders focus on efficient product delivery (instead of collections of technical tasks).
Pro Provides time taken for each step
Eg:
./1.setup.sh 48s
./2.build.sh 56s
With this information, it's easy to find out which line of the script is the bottleneck of the build process.
Pro Great Jira integration
The same company Atlassian built Jira, which provides top-tier integration with Jira.
Pro Combined service: source control and CI
Cons
Con Need Scripts for everything
Almost all operations are shell based, they are not configurations possible, your CI is as good as your scripting

Con Does not offer many plugins
Since it's relatively new and not very popular, there are few plugins available in GoCD.
Con Somewhat tricky to setup
Con Only 50 mins/month free usage
The Free plan only gives you 50 minutes per month to run the build.
Con Sparse documentation and examples
