Blue Ocean聽vs聽Jenkins

Need advice about which tool to choose?Ask the StackShare community!

Blue Ocean

+ 1

+ 1
Add tool

Blue Ocean vs Jenkins: What are the differences?

What is Blue Ocean? 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.

What is Jenkins? An extendable open source continuous integration server. In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.

Blue Ocean and Jenkins can be primarily classified as "Continuous Integration" tools.

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, Jenkins provides the following key features:

  • Easy installation
  • Easy configuration
  • Change set support

"Beautiful interface" is the primary reason why developers consider Blue Ocean over the competitors, whereas "Hosted internally" was stated as the key factor in picking Jenkins.

Blue Ocean and Jenkins are both open source tools. It seems that Jenkins with 13.3K GitHub stars and 5.48K forks on GitHub has more adoption than Blue Ocean with 2.49K GitHub stars and 435 GitHub forks.

Facebook, Netflix, and Instacart are some of the popular companies that use Jenkins, whereas Blue Ocean is used by CityLiv, Nexus National Security Network, and iCodeBetter. Jenkins has a broader approval, being mentioned in 1774 company stacks & 1526 developers stacks; compared to Blue Ocean, which is listed in 4 company stacks and 10 developer stacks.

Advice on Blue Ocean and Jenkins
Needs advice
Azure PipelinesAzure Pipelines

We are currently using Azure Pipelines for continous integration. Our applications are developed witn .NET framework. But when we look at the online Jenkins is the most widely used tool for continous integration. Can you please give me the advice which one is best to use for my case Azure pipeline or jenkins.

See more
Replies (1)

If your source code is on GitHub, also take a look at Github actions.

See more
Mohammad Hossein Amri
Chief Technology Officer at Axceligent Solutions | 3 upvotes 路 265K views
Needs advice

I'm open to anything. just want something that break less and doesn't need me to pay for it, and can be hosted on Docker. our scripting language is powershell core. so it's better to support it. also we are building dotnet core in our pipeline, so if they have anything related that helps with the CI would be nice.

See more
Replies (1)
Ankit Malik
Software Developer at CloudCover | 1 upvotes 路 247.6K views

Google cloud build can help you. It is hosted on cloud and also provide reasonable free quota.

See more
Needs advice

I'm planning to setup complete CD-CD setup for spark and python application which we are going to deploy in aws lambda and EMR Cluster. Which tool would be best one to choose. Since my company is trying to adopt to concourse i would like to understand what are the lack of capabilities concourse have . Thanks in advance !

See more
Replies (1)
Maxi Krone
Cloud Engineer at fme AG | 2 upvotes 路 164.5K views

I would definetly recommend Concourse to you, as it is one of the most advanced modern methods of making CI/CD while Jenkins is an old monolithic dinosaur. Concourse itself is cloudnative and containerbased which helps you to build simple, high-performance and scalable CI/CD pipelines. In my opinion, the only lack of skills you have with Concourse is your own knowledge of how to build pipelines and automate things. Technincally there is no lack, i would even say you can extend it way more easily. But as a Con it is more easy to interact with Jenkins if you are only used to UIs. Concourse needs someone which is capable of using CLIs.

See more
Needs advice
JenkinsJenkinsTravis CITravis CI

From a StackShare Community member: "Currently we use Travis CI and have optimized it as much as we can so our builds are fairly quick. Our boss is all about redundancy so we are looking for another solution to fall back on in case Travis goes down and/or jacks prices way up (they were recently acquired). Could someone recommend which CI we should go with and if they have time, an explanation of how they're different?"

See more
Replies (6)
Dustin Falgout
Developer at Elegant Themes | 13 upvotes 路 281.3K views

We use CircleCI because of the better value it provides in its plans. I'm sure we could have used Travis just as easily but we found CircleCI's pricing to be more reasonable. In the two years since we signed up, the service has improved. CircleCI is always innovating and iterating on their platform. We have been very satisfied.

See more
Peter Thomas
Distinguished Engineer at Intuit | 9 upvotes 路 260.7K views
Travis CITravis CI

As the maintainer of the Karate DSL open-source project - I found Travis CI very easy to integrate into the GitHub workflow and it has been steady sailing for more than 2 years now ! It works well for Java / Apache Maven projects and we were able to configure it to use the latest Oracle JDK as per our needs. Thanks to the Travis CI team for this service to the open-source community !

See more

I use Google Cloud Build because it's my first foray into the CICD world(loving it so far), and I wanted to work with something GCP native to avoid giving permissions to other SaaS tools like CircleCI and Travis CI.

I really like it because it's free for the first 120 minutes, and it's one of the few CICD tools that enterprises are open to using since it's contained within GCP.

One of the unique things is that it has the Kaniko cache, which speeds up builds by creating intermediate layers within the docker image vs. pushing the full thing from the start. Helpful when you're installing just a few additional dependencies.

Feel free to checkout an example: Cloudbuild Example

See more
Travis CITravis CI

I use Travis CI because of various reasons - 1. Cloud based system so no dedicated server required, and you do not need to administrate it. 2. Easy YAML configuration. 3. Supports Major Programming Languages. 4. Support of build matrix 6. Supports AWS, Azure, Docker, Heroku, Google Cloud, Github Pages, PyPi and lot more. 7. Slack Notifications.

See more
Oded Arbel
GitLab CIGitLab CI

You are probably looking at another hosted solution: Jenkins is a good tool but it way too work intensive to be used as just a backup solution.

I have good experience with Circle-CI, Codeship, and Travis (as well as problematic experiences with all of them), but my go-to tool is Gitlab CI: simple, powerful and if you have problems with their limitations or pricing, you can always install runners somewhere and use Gitlab just for scheduling and management. Even if you don't host your git repository at Gitlab, you can have Gitlab pull changes automatically from wherever you repo lives.

See more

If you are considering Jenkins I would recommend at least checking out Buildkite. The agents are self-hosted (like Jenkins) but the interface is hosted for you. It meshes up some of the things I like about hosted services (pipeline definitions in YAML, managed interface and authentication) with things I like about Jenkins (local customizable agent images, secrets only on own instances, custom agent level scripts, sizing instances to your needs).

See more
Decisions about Blue Ocean and Jenkins
Pedro Gil Carvalho
Head of Engineering at Lengoo GmbH | 6 upvotes 路 28.1K views

We replaced Jenkins with Github Actions for all our repositories hosted on Github. GA has two significant benefits for us compared to an external build tool: it's simpler, and it sits at eye level.

Its simplicity and smooth user experience makes it easier for all developers to adopt, giving them more autonomy.

Sitting at eye level means it's completely run and configured right alongside the code, so that it's easier to observe and adjust our builds as we go.

These two benefits have made "the build" less of a system engineer responsibility and more of a developer tool, giving developers more ownership from code to release.

See more
Kirill Mikhailov

Jenkins is a friend of mine. 馃榾

There are not much space for Jenkins competitors for now from my point of view. With declarative pipelines now in place, its super easy to maintain them and create new ones(altho I prefer scripted still). Self-hosted, free, huge community makes it the top choice so honestly for me it was an easy pick.

See more
Stephen Badger | Vital Beats
Senior DevOps Engineer at Vital Beats | 2 upvotes 路 109.7K views

Within our deployment pipeline, we have a need to deploy to multiple customer environments, and manage secrets specifically in a way that integrates well with AWS, Kubernetes Secrets, Terraform and our pipelines ourselves.

Jenkins offered us the ability to choose one of a number of credentials/secrets management approaches, and models secrets as a more dynamic concept that GitHub Actions provided.

Additionally, we are operating Jenkins within our development Kubernetes cluster as a kind of system-wide orchestrator, allowing us to use Kubernetes pods as build agents, avoiding the ongoing direct costs associated with GitHub Actions minutes / per-user pricing. Obviously as a consequence we take on the indirect costs of maintain Jenkins itself, patching it, upgrading etc. However our experience with managing Jenkins via Kubernetes and declarative Jenkins configuration has led us to believe that this cost is small, particularly as the majority of actual building and testing is handled inside docker containers and Kubernetes, alleviating the need for less supported plugins that may make Jenkins administration more difficult.

See more

Jenkins is a pretty flexible, complete tool. Especially I love the possibility to configure jobs as a code with Jenkins pipelines.

CircleCI is well suited for small projects where the main task is to run continuous integration as quickly as possible. Travis CI is recommended primarily for open-source projects that need to be tested in different environments.

And for something a bit larger I prefer to use Jenkins because it is possible to make serious system configuration thereby different plugins. In Jenkins, I can change almost anything. But if you want to start the CI chain as soon as possible, Jenkins may not be the right choice.

See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Blue Ocean
Pros of Jenkins
  • 7
    Beautiful interface
  • 521
    Hosted internally
  • 465
    Free open source
  • 314
    Great to build, deploy or launch anything async
  • 243
    Tons of integrations
  • 210
    Rich set of plugins with good documentation
  • 109
    Has support for build pipelines
  • 72
    Open source and tons of integrations
  • 63
    Easy setup
  • 61
    It is open-source
  • 54
    Workflow plugin
  • 11
    Configuration as code
  • 10
    Very powerful tool
  • 9
    Many Plugins
  • 8
    Continuous Integration
  • 8
    Great flexibility
  • 8
    Git and Maven integration is better
  • 6
    Github integration
  • 6
    100% free and open source
  • 6
    Slack Integration (plugin)
  • 5
    Easy customisation
  • 5
    Self-hosted GitLab Integration (plugin)
  • 4
    Docker support
  • 3
    Excellent docker integration
  • 3
    Platform idnependency
  • 3
    Fast builds
  • 3
    Pipeline API
  • 2
  • 2
    Can be run as a Docker container
  • 2
    It`w worked
  • 2
  • 2
    Hosted Externally
  • 2
    It's Everywhere
  • 2
    AWS Integration
  • 1
    NodeJS Support
  • 1
    PHP Support
  • 1
    Ruby/Rails Support
  • 1
    Universal controller
  • 1
    Easily extendable with seamless integration
  • 1
    Build PR Branch Only

Sign up to add or upvote prosMake informed product decisions

Cons of Blue Ocean
Cons of Jenkins
    Be the first to leave a con
    • 12
      Workarounds needed for basic requirements
    • 8
      Groovy with cumbersome syntax
    • 6
      Limited abilities with declarative pipelines
    • 6
      Plugins compatibility issues
    • 5
      Lack of support
    • 4
      No YAML syntax
    • 2
      Too tied to plugins versions

    Sign up to add or upvote consMake informed product decisions

    What is Blue Ocean?

    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.

    What is Jenkins?

    In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.

    Need advice about which tool to choose?Ask the StackShare community!

    What companies use Blue Ocean?
    What companies use Jenkins?
    See which teams inside your own company are using Blue Ocean or Jenkins.
    Sign up for Private StackShareLearn More

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Blue Ocean?
    What tools integrate with Jenkins?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    Blog Posts

    Mar 24 2021 at 12:57PM


    Dec 4 2019 at 8:01PM


    What are some alternatives to Blue Ocean and Jenkins?
    It is both an imperative and functional programming language. Its syntax and general usage overlaps that of the interpreted Rebol language.
    Jenkins X
    Jenkins X is a CI/CD solution for modern cloud applications on Kubernetes
    Travis CI
    Free for open source projects, our CI environment provides multiple runtimes (e.g. Node.js or PHP versions), data stores and so on. Because of this, hosting your project on means you can effortlessly test your library or applications against multiple runtimes and data stores without even having all of them installed locally.
    Continuous integration and delivery platform helps software teams rapidly release code with confidence by automating the build, test, and deploy process. Offers a modern software development platform that lets teams ramp.
    GitLab CI
    GitLab offers a continuous integration service. If you add a .gitlab-ci.yml file to the root directory of your repository, and configure your GitLab project to use a Runner, then each merge request or push triggers your CI pipeline.
    See all alternatives