Need advice about which tool to choose?Ask the StackShare community!
Blue Ocean vs TeamCity: What are the differences?
Developers describe Blue Ocean as "A reboot of the Jenkins CI/CD User Experience". Designed from the ground up for Jenkins Pipeline and compatible with Freestyle jobs, Blue Ocean reduces clutter and increases clarity for every member of your team. On the other hand, TeamCity is detailed as "TeamCity is an ultimate Continuous Integration tool for professionals". TeamCity is a user-friendly continuous integration (CI) server for professional developers, build engineers, and DevOps. It is trivial to setup and absolutely free for small teams and open source projects.
Blue Ocean and TeamCity belong to "Continuous Integration" category of the tech stack.
Some of the features offered by Blue Ocean are:
- Sophisticated visualizations of CD pipelines, allowing for fast and intuitive comprehension of software pipeline status.
- Pipeline editor (In Development) that makes automating CD pipelines approachable by guiding the user through an intuitive and visual process to create a pipeline.
- Personalization of the Jenkins UI to suit the role-based needs of each member of the DevOps team.
On the other hand, TeamCity provides the following key features:
- Automate code analyzing, compiling, and testing processes, with having instant feedback on build progress, problems, and test failures, all in a simple, intuitive web-interface
- Simplified setup: create projects from just a VCS repository URL
- Run multiple builds and tests under different configurations and platforms simultaneously
"Beautiful interface" is the top reason why over 4 developers like Blue Ocean, while over 52 developers mention "Easy to configure" as the leading cause for choosing TeamCity.
Blue Ocean is an open source tool with 2.49K GitHub stars and 435 GitHub forks. Here's a link to Blue Ocean's open source repository on GitHub.
According to the StackShare community, TeamCity has a broader approval, being mentioned in 171 company stacks & 51 developers stacks; compared to Blue Ocean, which is listed in 4 company stacks and 10 developer stacks.
Pros of Blue Ocean
- Beautiful interface7
Pros of TeamCity
- Easy to configure60
- Reliable and high-quality37
- User friendly31
- Github integration31
- On premise31
- Great UI18
- Smart16
- Can run jobs in parallel12
- Free for open source12
- Crossplatform8
- Great support by jetbrains4
- Chain dependencies4
- REST API4
- Fully-functional out of the box4
- Projects hierarchy4
- Build templates3
- Per-project permissions3
- Personal notifications3
- Free for small teams3
- 100+ plugins3
- Ide plugins2
- GitLab integration2
- Build progress messages promoting from running process2
- Artifact dependencies2
- Smart build failure analysis and tracking2
- Upload build artifacts2
- Built-in artifacts repository1
- Powerful build chains / pipelines1
- TeamCity Professional is FREE1
- Repository-stored, full settings dsl with ide support1
- Hosted internally0
- Official reliable support0
- High-Availability0
Sign up to add or upvote prosMake informed product decisions
Cons of Blue Ocean
Cons of TeamCity
- User friendly2
- Proprietary1
- High costs for more than three build agents1
- User-friendly1
Sign up to add or upvote consMake informed product decisions
What is Blue Ocean?
What is TeamCity?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Blue Ocean?
What companies use TeamCity?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Blue Ocean?
What tools integrate with TeamCity?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+22
+46
+35